Induction unit and label generator

ABSTRACT

Systems described herein for controlling, requesting, and coordinating the creation and generation of labels can be a label broker, providing a centralized location for storing label information created by various entities, and managing the requests for generation of physical labels coming from various sources and entities.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication Ser. No. 62/492,633, filed May 1, 2017 and entitled“INDUCTION UNIT AND LABEL GENERATOR,” and U.S. Provisional PatentApplication Ser. No. 62/536,073, filed Jul. 24, 2017 and entitled“INDUCTION UNIT AND LABEL GENERATOR,” both of which are hereby expresslyincorporated by reference in its entirety. Furthermore, any and allpriority claims identified in the Application Data Sheet, or anycorrection thereto, are hereby incorporated by reference under 37 C.F.R.§ 1.57.

BACKGROUND Field

The current disclosure relates to the field of induction of items into adistribution network and the associated labels for shipping and payment.

Description of the Related Art

Item distribution generally requires an indication on an item of thedestination and indicia of payment for distribution of the item. Someindividuals or entities wishing to ship items may not have the means forgenerating a label having computer-readable indicia thereon. Systems andmethods described herein relate to item deposit receptacles and labelcreation and generation.

SUMMARY

The systems, methods, and devices of the disclosure each have severalinnovative aspects, no single one of which is solely responsible for thedesirable attributes disclosed herein. In one innovative aspect a systemfor labeled induction of an item into a distribution network. The systemincludes: a label provider configured to receive, from a sendercommunication device, a request for a label to distribute an item via adistribution network. The label provider is further configured create alabel based on the request for the label and transmit, to a distributionserver, the created label for the item. The system also includes thedistribution server which is in communication with the label provider.The distribution server is configured to receive, from the labelprovider, the created label. The distribution server is configured toreceive generate a machine-readable identifier for the label. Thedistribution server is also configured to receive store, in a datastorage device, the created label and an association between the createdlabel and the machine-readable identifier. The distribution server isconfigured to receive, from an induction communication device, themachine-readable identifier for the label. The distribution server isfurther configured to receive retrieve the created label from the datastorage device based at least in part on the machine-readableidentifier. The distribution server is configured to receive cause, viathe induction communication device, generation of a physical label basedat least in part on the created label retrieved from the data storagedevice, where the generation of the physical label is deferred for aperiod of time subsequent to the generation of the machine-readableidentifier. Other embodiments of this aspect include correspondingcomputer systems, apparatus, and computer programs recorded on one ormore computer storage devices, each configured to perform the actions ofthe methods.

Implementations may include one or more of the following features. Thedistribution server may be further configured to: receive, via theinduction communication device, a confirmation that the physical labelhas been created; and store, in the data storage device, an indicator inassociation with the machine-readable identifier, where the indicatorindicates that the physical label has been created. The distributionserver may be further configured to: receive, from another communicationdevice, the machine-readable identifier for the label; determine, basedon the indicator and the machine-readable identifier, that the physicallabel has been created; and transmit a message to the anothercommunication device indicating that the physical label has beencreated. In some implementations of the system, the label may include asender address identifying a location from which the item is beingdistributed. The distribution server may be further configured to:receive, from the induction communication device, location informationfor the induction communication device; determine that the locationinformation for the induction communication device is within a thresholddistance of the sender address, where the physical label is generated inresponse to determining that the location information is within thethreshold distance of the sender address.

Additionally or alternatively, the distribution server may be configuredto: receive, from a scanning device, scanned information from thephysical label; confirm that the scanned information corresponds to theitem; and route the item to an item processing equipment for adistribution network based at least in part on the scanned information.The physical label may include an identifier indicating that thephysical label was generated by the distribution server based on arequest from the label provider. The item processing equipment mayinclude a postage canceler, and where the distribution server isconfigured to route the item to bypass the postage canceler in responseto receiving the confirmation.

The system may include an induction receptacle for storing an item,where the induction receptacle includes: a locking means for securingthe induction receptacle; and a scanning device for detectinginformation from the physical label. The distribution server may befurther configured to: receive, from the scanning device, scannedinformation from the physical label; retrieve a disposition status forthe item from the data storage device based at least in part on thescanned information, where the disposition status indicates whether theitem has been inducted into the distribution network; determine that theitem has not been inducted to the distribution network based at least inpart on the disposition status; and transmit a message to the lockingmeans, where the message causes the locking means to permit access tothe induction receptacle.

Some embodiments of the system may include a labeling kiosk. Thelabeling kiosk may include an input interface for receiving machinereadable identifiers for labels, where receiving the machine-readableidentifier includes receiving the machine-readable identifier from thelabeling kiosk. The induction communication device may include thelabeling kiosk. The input interface may include at least one of: (a) ascanning device; or (b) a graphical user interface. The created labelmay include a data file containing information for generating thephysical label. For example, the created label may include an image ofthe label. In some implementations, receiving the machine-readableidentifier may include receiving the machine readable identifier from aportable, handheld scanning device associated with a distributionresource of the distribution network. The distribution server may befurther configured to transmit, to the sender communication device, themachine-readable identifier for the label. Additionally oralternatively, the distribution server may be further configured totransmit, to the label provider, the machine-readable identifier for thelabel. The innovative features described may include or be implementedby hardware, a method or process, or computer software on acomputer-accessible medium.

In another innovative aspect a system for labeled induction of an iteminto a distribution network is provided. The system includes one or moreprocessing devices; and a computer-readable storage medium storingmachine readable instructions that, when executed by the one or moreprocessing devices, cause the system to receive, from a label provider,information for creating a label for distributing an item via adistribution network. The instructions also cause the system to create alabel using the information for creating the label. The instructionsalso cause the system to generate a machine-readable identifier for thelabel. The instructions also cause the system to store, in a datastorage device, the created label and an association between the createdlabel and the machine-readable identifier. The instructions furthercause the system to transmit, to a first communication device, themachine-readable identifier for the label. The instructions also causethe system to receive, from a second communication device, themachine-readable identifier for the label. The instructions also causethe system to retrieve the created label from the data storage devicebased at least in part on the machine-readable identifier. Theinstructions also cause the system to cause, via the secondcommunication device, generation of a physical label based at least inpart on the created label. Other embodiments of this aspect includecorresponding computer systems, apparatus, and computer programsrecorded on one or more computer storage devices, each configured toperform the actions of the methods.

Implementations may include one or more of the following features. Themachine-readable instructions, when executed by the one or moreprocessing devices, may further cause the system to at least: receive,via the second communication device, a confirmation that the physicallabel has been generated; and store, in the data storage device, anindicator in association with the machine-readable identifier, where theindicator indicates that the physical label has been generated. Themachine-readable instructions, when executed by the one or moreprocessing devices, may further cause the system to at least: receive,from another communication device, the machine-readable identifier forthe label; retrieve, from the data storage device, a disposition statusfor the item associated with the label based at least in part on themachine-readable identifier; determine that the disposition statuscorresponds to an unauthorized status indicating that the label is nolonger authorized for inducting the item to the distribution network;and transmit a message to the another communication device indicatingthat the label is unauthorized.

The machine-readable instructions, when executed by the one or moreprocessing devices, may, in some embodiments, further cause the systemto at least: receive a sender address identifying a location from whichthe item is being distributed, receive, from the second communicationdevice, location information for the second communication device; anddetermine that the location information for the second communicationdevice is within a threshold distance of the sender address, where thephysical label is generated in response to determining that the locationinformation is within the threshold distance of the sender address. Inone embodiment of the system, the physical label includes an identifierindicating that the physical label was generated based on a request fromthe label provider, and where the distribution network includes apostage canceler, and where the machine-readable instructions, whenexecuted by the one or more processing devices, further cause the systemto at least route the item to bypass the postage canceler based at leastin part on a disposition status for the item.

Some implementations of the system include an induction receptacle forstoring an item, where the induction receptacle includes: a lockingmeans for securing the induction receptacle; and a scanning device fordetecting information from the physical label. The machine-readableinstructions, when executed by the one or more processing devices, mayfurther cause the system to at least: receive, from the scanning device,scanned information from the physical label; retrieve a dispositionstatus for the item from the data storage device based at least in parton the scanned information, where the disposition status indicateswhether the item has been inducted into the distribution network;determine that the item has not been inducted to the distributionnetwork based at least in part on the disposition status; and transmit amessage to the locking means, where the message causes the locking meansto permit access to the induction receptacle. In one embodiment, theinduction receptacle may include measurement means configured to collectmeasurement information a physical characteristic of the item.

The information for creating the label may include a specified value forthe physical characteristic (e.g., weight, size, packaging). Themachine-readable instructions, when executed by the one or moreprocessing devices, may further cause the system to at least: store, inthe data storage device, the specified value in association with themachine-readable identifier; retrieve, from the data storage device, thespecified value for the label based at least in part on themachine-readable identifier; and determine that the measurementinformation corresponds to the specified value for the physicalcharacteristic, where the message is transmitted after determining thatthe measurement information corresponds to the specified value. Theinnovative features described may include or be implemented by hardware,a method or process, or computer software on a computer-accessiblemedium.

The foregoing is a summary and thus contains, by necessity,simplifications, generalization, and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent in theteachings set forth herein. The summary is provided to introduce aselection of concepts in a simplified form that are further describedbelow in the Detailed Description. This summary is not intended toidentify key features or essential features of the claimed subjectmatter, nor is it intended to be used as an aid in determining the scopeof the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features of the present disclosure will becomemore fully apparent from the following description and appended claims,taken in conjunction with the accompanying drawings. Understanding thatthese drawings depict only several embodiments in accordance with thedisclosure and are not to be considered limiting of its scope, thedisclosure will be described with additional specificity and detailthrough use of the accompanying drawings.

FIG. 1 is a perspective view of an embodiment of an item receptacle inan in-wall type installation.

FIG. 2 is a block diagram of a system for operating and using an itemreceptacle and for label creation and generation showing an arrangementof drawing sections 2-1, 2-2, and 2-3.

FIG. 2-1 depicts a first section of a system for operating and using anitem receptacle and for label creation and generation with connectionsto FIGS. 2-2 and 2-3, according to the arrangement of FIG. 2.

FIG. 2-2 depicts a second section for operating and using an itemreceptacle and for label creation and generation with connections toFIGS. 2-1 and 2-3, according to the arrangement of FIG. 2.

FIG. 2-3 depicts a third section for operating and using an itemreceptacle and for label creation and generation with connections toFIGS. 2-1 and 2-2, according to the arrangement of FIG. 2.

FIG. 3 is a block diagram of an item receptacle system.

FIG. 4 is an embodiment of a label for use in item distribution.

FIG. 5A is a flowchart depicting an embodiment of a process 500 forcreating a label

FIG. 5B is a flowchart depicting an embodiment of process for creating alabel.

FIG. 6 is a flow chart depicting an embodiment of a process forgenerating a label.

FIG. 7 is a flow chart depicting an embodiment of a process forgenerating label a label using a mobile delivery device.

FIG. 8 depicts an arrangement of FIGS. 8-1, 8-2, and 8-3, which depictan exemplary process flow diagram showing data flows between entities inthe system of FIGS. 2-1, 2-2, and 2-3.

FIG. 8-1 depicts a first section of an exemplary process flow diagramshowing data flows between entities, and shows connections to FIG. 8-2according to the arrangement of FIG. 8.

FIG. 8-2 depicts a first section of an exemplary process flow diagramshowing data flows between entities, and shows connections to FIG. 8-1and FIG. 8-3 according to the arrangement of FIG. 8.

FIG. 8-3 depicts a first section of an exemplary process flow diagramshowing data flows between entities, and shows connections to FIG. 8-2according to the arrangement of FIG. 8.

FIG. 9 depicts an arrangement of FIGS. 9-1, 9-2, 9-3, 9-4, 9-5, and 9-6,which depict an exemplary process flow diagram showing data flowsbetween entities for label generation.

FIG. 9-1 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIGS. 9-2 and 9-3 according to the arrangement of FIG. 9.

FIG. 9-2 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIG. 9-1 according to the arrangement of FIG. 9.

FIG. 9-3 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIGS. 9-1 and 9-4 according to the arrangement of FIG. 9.

FIG. 9-4 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIG. 9-3 according to the arrangement of FIG. 9.

FIG. 9-5 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIGS. 9-3 and 9-6 according to the arrangement of FIG. 9.

FIG. 9-6 depicts a first section of an exemplary process flow diagramshowing data flows between entities for label generation, and showsconnections to FIG. 9-5 according to the arrangement of FIG. 9.

FIG. 10 is an example interface for requesting production of a physicallabel.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe Figures, may be arranged, substituted, combined, and designed in awide variety of different configurations, all of which are explicitlycontemplated and make part of this disclosure.

Reference in the specification to “one embodiment,” “an embodiment,” or“in some embodiments” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the invention. Moreover, the appearance ofthese or similar phrases throughout the specification does notnecessarily mean that these phrases all refer to the same embodiment,nor are separate or alternative embodiments necessarily mutuallyexclusive. Various features are described herein which may be exhibitedby some embodiments and not by others. Similarly, various requirementsare described which may be requirements for some embodiments but may notbe requirements for other embodiments.

As used herein, an item can be a parcel, a package, an envelope, a flat,a mailpiece, a box, a suitcase, or any other item that can betransported from one location to another by a distribution entity. Adistribution entity may be an entity engaged in transporting items fromone location to another, such as the United States Postal Service(USPS), another commercial carrier, a storage facility, a fulfillmentwarehouse, a luggage sorting facility, or any other similar facility,company, or entity.

Using the USPS as an example, an item, such as a parcel, mailpiece, orthe like has a label thereon, or information printed directly on theitem (also referred to as a label herein), which indicates, among otherthings, a sender, a delivery point (destination), a class of service,postage, and a tracking code. The labels include computer-readable codeswhich encode the above items of information. The information containedin the computer-readable code must be regulated and formatted uniformlyin order to be read, understood, and processed within the USPS'sdistribution networks. Entities including the USPS and other entitiescan create labels which include postage and other information, fordistribution within the USPS. As used herein, creating a label can referto the process for producing or making an electronic label, such as anelectronic image of a label, a data file including label information,and the like. The USPS and other entities can be enabled to generatelabels, that is, can print physical embodiments of the created labelsand attach the labels to the items. As used herein, generating a labelcan refer to the process of producing, making, or printing a physicalembodiment of a label. Generating the label can include obtainingelectronic information from the created label in order to produce thephysical label, as will be described herein. Some generating entitiesare involved with processing the label and postage, but do not haveaccess to the physical item to be shipped. Additionally, some entities,such as individuals or businesses may wish to print their own labels,rather than going to the post office or other distribution facility. Insuch an instance, the user requests creation of a label for a particularitem. The created label will include a destination and a postageindicia, and the label information can be sent to the individual orbusiness for generation/printing and attaching to the item to be sent.

Systems described herein for controlling, requesting, and coordinatingthe creation and generation of labels can be a label broker, providing acentralized location for storing label information created by variousentities, and managing the requests for generation of physical labelscoming from various sources and entities.

Some entities, such as an individual or business wishing to send an itemvia a distribution network may have computer capabilities, but may nothave printing capabilities or may not wish to print the label. In suchan instance, the sending entity can request a shipping label be created,pay postage, and prepare the item for shipping. The entity can then goto a post office or to an item receptacle, such as an item inductionunit, which has label printing capability. The entity can requestcreation generation of a label (e.g., printing a physical label) at anitem receptacle such as at a self-serve location, without needing to goto and wait in line at a post office or other shipping facility.

FIG. 1 depicts an embodiment of an item receptacle 100 installed in awall 105. The item receptacle 100 includes an item receiving portion 110(shown in a closed position), including a rotatable drum 112 and ahandle 114. The item receptacle 100 further includes a user interface120. The user interface 120 provides an input interface to request orreceive information for distributing an item. The user interface 120includes a screen 122, a sensor 124, a payment device 126, a printer128, and an input interface 130. The item receptacle 100 and the userinterface 120, as well as their subcomponents, may be connected to andin communication with computer elements (not shown) of the itemreceptacle 100, such as one or more processors and/or memory circuits,which will be described in greater detail with reference to FIG. 3. Theitem receptacle 100 may be similar to and operate similar thosedescribed in U.S. Provisional Patent Application No. 62/374,190,entitled Smart Drop Box and filed Aug. 12, 2016, the entire contents ofwhich are hereby incorporated by reference.

The item receiving portion 110 is configured to receive an item withinthe drum 112 when rotated to an open position, and can further beconfigured to automatically drop the item into a box, bin, or othercollection container behind the wall 105 when the drum 112 is returnedto a closed position. For example, in some embodiments, the wall drum112 can be a cylinder mounted partially in the wall so as to rotateabout a longitudinal axis passing through the two circular end faces ofthe cylinder. The drum 112 can include a cavity or opening in the sideof the cylinder, configured to receive an item. In one example, thecavity can include a radial wedge-shaped portion of the cylinder. Thecavity can be positioned such that the cavity is exposed to the outsidewhen the drum 112 is in an open position. The cavity can further beconfigured to allow an item within the cavity to fall out of the drum112 and into a collection container due to gravity, when the drum 112 isin a closed position. The drum 112 can be rotated from the closedposition shown to an open position by moving the handle 114 downward. Anintermediate position can be a rotational position between the openposition and the closed position. For example, an intermediate positionmay be relatively close to the closed position so as to prevent a userfrom taking an item out of the drum 112, while also being far enoughfrom the closed position such that gravity does not cause the itemwithin the drum 112 to fall into the collection container.

In some embodiments, the item receiving portion 110 can be configured toopen similar to a locker, have a roll-up door, or be of another desiredconfiguration which is capable of opening, receiving an item, andclosing such that, after an item is deposited in the item receivingportion 110, the item is not accessible to another user or entity. Itwill be understood that the item receptacle or item induction unit canhave a variety of configurations without departing from the scope of thepresent disclosure.

The item receiving portion 110 may be configured to be operablemanually, such as by a user of the item receptacle 100 rotating the drum112 by the handle 114. In some embodiments, the item receiving portion110 may be configured to be operated automatically by one or more motors(not shown) controlled by computer elements of the item receptacle 100.The item receptacle 100 may further include one or more locks (notshown) controlled by computer elements of the item receptacle 100 andconfigured to prevent the drum 112 from rotating. The one or more locksmay be configured to lock the drum 112 in an open position, a closedposition, and/or an intermediate position between open and closed. Forexample, an intermediate position may be sufficiently closed to preventan item in the drum 112 from being removed (e.g., “trapping” the item),while being far enough from a fully closed position that the item in thedrum does not drop from the drum 112 into the collection container. Aswill be described in greater detail with reference to FIGS. 4 and 5, anintermediate position may advantageously allow the item receptacle 100to secure an item for verification of postage, size, and/or weight,while also allowing the item receiving portion 110 to return the item toa user if acceptance of the item is rejected by the item receptacle 100or by the user.

The user interface 120 can be configured for various purposes related toreceipt, deposit, labelling, shipping, and item distribution. Forexample, the user interface 120 can be a display screen having aninterface 130. In some embodiments, the interface 130 can beincorporated into the user interface 120, such as a touch screeninterface, or can comprise a keypad, keyboard, one or more hard keys orsoft keys, and the like. The user interface 120 is configured to receiveuser input, providing user notification, and the like, as will bedescribed in greater detail below. In some embodiments, the screen 122may be only a display screen, or may be an interactive screen such as atouch screen configured to display graphic or text content and toreceive tactile input from a user. A keypad can be provided as analternative or additional input interface 130 if the screen 122 is atouch screen, or can be the primary input device if the screen 122 isnot capable of receiving input. The user interface 120 may comprise orbe implemented as a portable handheld scanning device to facilitate useby a delivery agent (e.g., postal carrier or other distributionresource) moving between locations.

The user interface 120 can include a near field communication,Bluetooth, or similar wireless protocol transfer capable of receivinginformation from a wireless computing device. The user interface 120 canconnect to the mobile computing device of a user, and the user caninteract with the item receptacle 100 from the user's mobile computingdevice, and can send information to and receive information from theuser interface 120.

The sensor 124 can be a scanning device such as a camera (e.g., a stillimage camera, a video camera, a webcam, etc.), an optical scanner, alaser barcode scanner, or any other optical signal acquisition device orcombination thereof. The sensor 124 may be configured to read payment orother information, such as a barcode or QR code on a label, printout,smartphone or tablet screen, and/or may be configured to take images forproof of deposit, such as an image of an item being deposited or of theperson depositing the item. The information read by the sensor 124 maybe referred to as scanned information.

The payment device 126 may be configured to accept payment. In someembodiments, the payment device 126 comprises one or more of a magneticor chip card reader, a near field communication device, a Bluetoothdevice or similar wireless communication protocol for receivingelectronic payment, a currency acceptor, and the like. For example,users intending to ship an item who have not prepaid for shippingservices may make the necessary payment (e.g., paying for postage) atthe item receptacle 100, and may provide payment at the payment device126. In some embodiments, the payment device 126 such as magnetic cardreader may further be configured to read magnetic media for purposesother than payment. For example, the magnetic card reader may beconfigured to read a magnetic strip on a driver's license or otheridentification card to verify the identity of a user.

The printer 128 can provide printed documents to a user, such as ashipping label, an acceptance verification receipt, a receipt forpurchase of shipping services, a payment indicia, such as postage, orother printed media. The printer 128 can print on a label having anadhesive on one side thereon. In some embodiments, the printer 128 canspray a label or code onto an item to be deposited. In some embodiments,the printer 128 can print a label, postage, computer-readable code andthe like on an item which has been deposited into the item receivingportion 110. In such embodiments, the printer 128 can comprise amoveable print head that can extend to contact a surface of the item tobe deposited, or the item after deposit.

Additionally, the item receptacle can include features in addition tocreation and generation of labels, including, for example, printingstamps. A user can purchase stamps via a website, or an applicationrunning on a smartphone. The application will provide acomputer-readable code when payment for postage has been confirmed. Theuser can provide the computer-readable code to the sensor 124, where theitem receptacle can confirm the computer-readable code as being a validstamp purchase. Stamps can then be printed at the printer 128, or byseparate component, such as a stamp printer (not shown).

FIG. 2 depicts a block diagram of a system 200 for operating and usingan item receptacle 100 and for label creation and generation. The system200 comprises a central hub 210. The central hub is in wired and/orwireless communication with a label provider system 220, a label requestsystem 230, and a user interface system 225.

The central hub 210 includes a processor 212, a memory 214, andcommunications modules 216. The processor 212 is configured to directthe activities of the central hub 210 and to execute programs stored inthe memory 214. The processor 212 processes communications to and fromthe label provider system 220, the label request system 230, and thereceptacle 100. The memory 214 can store operating instructions for theprocessor 212 and label information. In some embodiments, memory 214 isa dedicated storage device for storing label information, and operatinginstructions can be stored elsewhere within the central hub 210. In someembodiments, the memory 214 can comprise a database or other datastorage device for storing, managing, and providing label data uponrequest. As will be described in greater detail, the memory 214 canstore the date and time of creation of a label, whether the label hasexpired, whether the label has been generated, the date and time oflabel generation, disposition status for the item associated with thelabel, and/or any other desired information or indicators thereof. Eachtransaction, such as a label creation request, a label generationrequest, and the like, which system 200 performs can create a databaserecord including information taken from various components of system 200during the processes of creation and generation of labels. This databaserecord can be part of the label information stored in the memory 214, orit can be in addition to the label information stored in memory 214 andcan be associated with the label information stored in memory 214.

The communications modules 216 include a plurality of communicationspathways including inbound communications 217, requestor communications218, and outbound communications 219. Inbound communications 217 comefrom the label provider system 220, and include label information, aswill be described in greater detail below. Requestor communications 218come from the label request system 230 and include requests to generatephysical labels and include label information sent to label printers orother devices, as will be described in greater detail below. Outboundcommunications 219 are generally initiated by the central hub 210 andare sent to the label provider system 220. The outbound communications219 include updates to label status, label cancellation or expiration,label analytic information, and the like, as will be described ingreater detail below.

In some embodiments, inbound communications 217, requestorcommunications 218, and outbound communications 219 can be performed viaone or more APIs which allow the label providers with access to thecentral hub 210, and via which label providers (e.g., the label providersystem 220) can see the status of labels created, such as whether andwhen the labels have been generated, processed, inducted into thedistribution network, who generated the labels, and the like. Thecentral hub 210 may thus operate as a distribution server or labelbroker to coordinate the generation of physical labels and induction ofitems based thereon.

The label provider system 220 can include a postage provider 222, athird party provider 224, and/or an e-commerce merchant 226. The postageprovider 222, the third party provider 224 and the e-commerce merchant226 can create labels having label information thereon. Theselabel-provider entities can create these labels in response to a labelcreation requests via a label request communication connection 215coming from users, such as via an application or web site, which will bedescribed in greater detail below. The label provider system 220 cancreate labels and provide created label information to the central hub210, which can be stored in the memory 214. The postage provider 222 canbe a distribution network, such as the United States Postal Service(USPS). The third party provider 224 can be an entity that contractswith a distribution network to manage payment for distribution, such aspostage, or who manages postage and label creation. The e-commercemerchant 226 can be a retailer, wholesaler, or other similar merchantentity. The e-commerce merchant 226 can create labels which includelabel information for items sold to users, businesses, and otherentities. In some embodiments, the third party provider 224 and thee-commerce merchant 226 can create labels according to a format readableand/or usable by the distribution network, for example, the USPS.

The label provider system 220 can communicate with the central hub 210via a wired connection, a wireless connection, or a combination of both.In some embodiments, entities, for example, the postage provider 222,may be associated with the central hub 210, and may be under control ofthe distribution network. In some embodiments, entities, such as thethird party provider 224 and the e-commerce merchant 226 may be separateor distinct entities from the distribution network and which operateunder an agreement with the distribution entity. In such cases, thedistribution entity can provide rules and requirements relating to thelabel information, access to databases and payment systems, so thatcreated labels can be properly read and understood, and paymenttransacted when the item reaches the processing equipment of thedistribution entity. For example, the processing equipment may include apostage canceler configured to mark postage affixed to an item as usedthereby avoiding the reuse of the same postage for a different item.Since the system includes features for tracking the disposition statusof an item, including whether an item has been inducted to the systemusing a specific physical label, the postage canceler may be bypassed.The processing equipment may be configured to route an item to adestination location such as a receptacle for items within a geographicarea that includes the destination location for the item. Sorters,conveyors, drones, robots, or other automated devices may be adjustedbased on the information scanned from the physical label to ensure theitem is positioned for distribution.

The label request system 230 is in wired or wireless communication withthe central hub 210. The label request system 230 can include differentinduction communication devices, each of which is in communicatingconnection with the central hub 210. The induction communication devicescan be a computer terminal 232, such as at a retail location, a postoffice, website or online interface, and the like, a mobile deliverydevice 234, an item receptacle 238, a self-service kiosk, or anotherstationary or mobile computing device. The item receptacle 238 can besimilar to the item receptacle 100 or other induction receptaclesdescribed elsewhere herein and can be used interchangeably. The centralhub 210 may include a locator service which provides a machine interface(e.g., application programming interface) to provide discovery of itemreceptacles at or near a specific location which can be used fordeferred generation of physical labels as described. For example, thelocator server may receive a ZIP code, address, or other locationidentification information. The locator service may query a registry ofitem receptacles at or near the specified location. The query mayinclude a default distance or receive a distance as an input parameter.The query may provide information identifying those item receptacleswithin the default or specified distance to the specified location. Alisting of item receptacles may then be returned by the locator service.Additional information about an item receptacle may be included such ashours of operation, limitations on what can or cannot be inducted usingthe receptacle (e.g., letters only, item dimensions, etc.), or anoperator of the location (e.g., USPS, university, postal servicecompany, etc.).

The computer terminal 232 can be a home computer, laptop, or similardevice with internet connectivity. A user can access the label providersystem 220 to request creation of a label. In some embodiments, therequest to generate a label can be performed in an application residenton the computer terminal 232, in the mobile delivery device 234, or inthe item receptacle 238.

The mobile delivery device 234 can be a handheld or portable device usedby a carrier or other resource of the distribution network. In someembodiments, the mobile delivery device 234 can be a proprietary ordedicated device having specialized software or applications for use bya carrier which facilitates requests for generation of labels. In someembodiments, the mobile delivery device 234 can be a mobile computingdevice, such as a smartphone running applications which allow or assista carrier or other resource to perform their duties. The mobile deliverydevice 234 can also allow access to the central hub. The mobile deliverydevice 234 can comprise a scanner, such as a barcode scanner, an opticalscanner, a camera, or other similar input device. The mobile deliverydevice can also comprise an input device, such as a keyboard ortouchscreen. The mobile delivery device 234 can also include a printer,or can be in communication with a printer, which can generate a labelbased on information input into the mobile delivery device 234. In someembodiments, the printer associated with the mobile delivery device 234can be located remote from the mobile delivery device 234, such as on acarrier's vehicle or at a distribution network facility. The process ofcreation and generation of labels using a delivery device 234 will bedescribed in greater detail below.

The item receptacle 238 can be similar to those described above withregard to FIG. 1. The label request system 230 and the central hub 210are in communication with the item receptacle 238 via a wired orwireless connection, as will be described elsewhere herein.

The user interface system 225 can comprise a computing device that canbe used to request creation and/or generation of a label. Theseprocesses will be described in greater detail below. The user interfacesystem 225 can include, for example, a computer terminal 233 or a mobilecomputing device, such as a smartphone 236. When associated with asender of the item, the computing device may be referred to as a sendercommunication device.

In some embodiments the computer terminal 233 accesses an application ormodule configured to communicate with the label provider system 220,such as an application associated with the postage provider 222, thethird party provider 224, or the e-commerce merchant, and requestscreation of a label. In some embodiments, the request for creation oflabels can be provided to the central hub 210 via the label requestsystem 230. The request and creation of labels will be described ingreater detail below. The computer terminal 233 can access the labelprovider system 220 via a wired or wireless network. In someembodiments, the computer terminal 233 can access the label providersystem 220 via website or specialized application running on thecomputer terminal 233.

The smartphone 236 can be a tablet computer or cellular phone capable ofRF, 3G, 4G, LTE, Bluetooth, Wi-Fi, or other similar wirelesscommunication protocols. The smartphone 236 includes a display screen,is configured to run an application which communicates with the labelprovider system 220, and facilitates requesting creation of a label viathe label provider system 220. The application can also allow arequestor or user to update or modify labels which have been previouslygenerated, or which have been created and not yet generated. In someembodiments, the smartphone 236 can communicate with the central hub 210and request label creation from the label provider system 220 via thecentral hub 210. The process of creating and generating a label via thesmartphone 236 will be described in greater detail below.

FIG. 3 depicts a block diagram of a control system 302 for an itemreceptacle 300. The control system 302 comprises a processor 305 incommunication with a memory 315, a communication device 316, a userinterface 320, and an external image capture device 324, measurementmeans (e.g., an internal image capture device 330 or a scale 335) and amotor 338. The internal image capture device 330 and the scale 335 canbe located inside an item receiving compartment 312 of the itemreceptacle 300. The measurement means may collect measurementinformation for a physical characteristic of the item such as weight orsize. The measurement information may be compared to the declaredcharacteristics when the label was requested. In this way, the systemcan ensure that the item for which the label was requested correspondsto the item presented at the item receptacle 300. For example, the labelmay be requested for a weight of a specified value. If the weight of theitem presented at the item receptacle 300 does not correspond to thespecified value, the locking means securing the item receptacle 300 maynot release to permit induction of the item. Correspondence may includea tolerance such that the specified value is deemed to correspond if themeasured value is within the tolerance amount of the specified value.For example if the size was specified as 8″×4″×3″ and the item presentedis measured at 8.1″×4″×3″, if the tolerance amount was 0.1″, thediscrepancy between the specified value and the measured value may beignored. However, if the measured value was 9″×4″×3″, the values may bedeemed to be different enough to prohibit induction of the item usingthe label. If the measured amount is smaller than the specified value,it may be desirable to permit induction of the item since the servicepaid for would likely exceed the actual service provided for the smalleritem.

The motor 338 can be mechanically connected to the item receptacle so asto move, rotate, or operate the item receptacle. The item receptacle 300may be any device configured to receive an item, such as a wall drum ora locker, similar to those as described elsewhere herein. The internalimage capture device 330 and scale 335 can image and weigh items withinthe item receptacle 300 as described above. The motor 338 can provide amotive force to a rotatable drum, door, or other enclosing device on thereceptacle 300. The internal image capture device 330, the scale 335,and the motor 338 are in electrical communication with the processor305. In some embodiments, the receptacle 300 can be manually operatedand need not include a motor.

The processor 305 is configured to control and receive input from thememory 315, the communication device 316, the internal image capturedevice 330, the scale 335, the motor 338, the external image capturedevice 340, and the user interface 320. The memory 315 can store datareceived from the processor 305 and send data stored therein to theprocessor 305. The communication device 316 can facilitate the transferof information between the processor 305 and the network 350, such as bytransmitting and/or receiving data from the processor 305 and thenetwork 350.

The processor 305 can similarly control all functions of the itemreceptacle 300, the internal image capture device 330, the scale 335,the external image capture device 324, and the user interface 320 asdescribed elsewhere herein. For example, the user interface 320 candisplay a message on a display screen based on input received from theprocessor 305, and can transmit data to the processor, including inputreceived from a user. The user interface 320 comprises components for auser to input information to the item receptacle 300, such as akeyboard, touchscreen, and the like, and comprises components to outputinformation to a user, such as a display screen, a printer, audiospeakers, lights, and the like.

The item receptacle 300 can lock or unlock, receive one or more items,and transmit a status of the item receptacle 300 to the processor 305.The scale 335 can measure the weight of an item within the itemreceptacle 300 and can transmit a measured weight to the processor 305.The external image capture device 340 can take a picture of a user, aprinted or electronic document containing payment information, or anyother object within visual range of the external image capture device340. The internal image capture device 330 can take a picture of an itemwithin the item receptacle 300 and can scan or read a label or acomputer-readable code on an item within the item receptacle 300. Theprocessor 305 can receive data including images taken by the internalimage capture device 330 and the external image capture device 340,weight information from the scale 335, and/or user input received at theuser interface 320. The item receptacle 300 and all subcomponents may besimilar to the item receptacle described elsewhere herein.

The item receptacle 300 is in communication with a central hub 310 via anetwork 350 via the communication device 316. The network can be anycommunication network configured to transmit data, such as the internet,a local area network (LAN), wireless communication such as Wi-Fi,satellite communication, or any other network capable of transferringdata between the item receptacle 100 and the central hub 310. Thecentral hub 310 is configured to communicate with the database 314, suchas to retrieve payment information based on item information receivedfrom the communication device 316. In various embodiments, the centralhub 310 and the database 314 can be located within the control system302, separate from but directly electrically connected to the controlsystem 302, or in a location remote from the control system 302, such asa data facility configured to provide payment verification for aplurality of control systems. In some embodiments, the database 314and/or central hub 310 can include cloud computing and/or cloud storagefunctions. The central hub 310 and database 314 may be similar to thecentral hub 210 and database 314 described elsewhere herein.

The label provider 365 can communicate with the central hub 310 and/orthe item receptacle 300 via the network 350. For example, the labelprovider 365 may provide label information to the item receptacle 300via the network 350. Label information can be provided in a variety ofdata formats. For example, in some embodiments, the label provider 365can create a label and send the label information to the central hub 310and/or the item receptacle as an image file such as a .jpg, .gif, .pdf,and the like. In some embodiments, the label provider 365 can create alabel and send the label information to the central hub as a data filesuch as a mail.dat file, a computer-readable code encoding the labelinformation, a computer-readable code encoding a pointer oridentification of a data file containing the label information, fromwhich the label information can be extracted at the central hub 310 orat the item receptacle 300. As will be described herein below, the labelinformation from the created label can be received, read, converted ifnecessary, and generated as a physical label

FIG. 4 depicts an embodiment of a label 400. The label 400 includesseveral data fields with specific data and is arranged in a standardizedor mostly standardized format, for ease of use throughout a distributionnetwork. The label 400 comprises a sender identifier 402, a recipient404, computer-readable indicia 406, postage information 408, a trackingcode 410, and a service class identifier 412. A label of the presentdisclosure can contain none, some, or all of the fields described withregard to exemplary label 400. The label 400 can comprise any desirablecombination of label elements. For example, in some embodiments, postageinformation 408 may be omitted. In some embodiments, the label cancomprise only the computer-readable indicia 406.

The sender identifier 402 and recipient 404 can identify the sender ofthe item to which the generated label 400 will be or is affixed. Thesender identifier 402 can be a mailer identification number, a returnaddress, the address of the sender (e.g., sender address), or otherdesired information. The recipient 404 can be identified by a deliverypoint identifier, a street address, a virtual address, a recipientidentifier, and the like. The computer-readable indicia 406 can be amachine readable identifier, such as a one or two-dimensional barcode, afour state barcode, information-based indicia barcode, or other barcode,or any other desired computer-readable code. The computer-readableindicia 406 can encode one or more pieces of information from the label400, such as the sender identifier 402, the recipient 404, postageinformation 408, the service class identifier 412, or any combinationthereof. In some embodiments, the computer-readable indicia can encodean identifier of the item receptacle 100 where the label was generated,an identifier of the entity requesting generation of the label, anidentifier of the entity creating the label, or any combination ofthese. In some embodiments, the computer-readable indicia can comprise alabel key, as will be described elsewhere herein. In some embodiments,the label key can be located on the label separate from thecomputer-readable indicia 406.

The computer-readable indicia 406 can also include a unique identifiercomponent which associates a label with the item on which the label isplaced. For example, where 10 parcels are addressed to the samerecipient or delivery point, the computer-readable indicia will includea similar or identical portion for each of the 10 parcels, whichidentifies the delivery point, the sender, and/or any other desiredinformation. For these 10 parcels, an additional field or encoding canbe present in the computer-readable indicia 406 which uniquelyidentifies each item of the 10 items. In this example, the label 400 caninclude an additional field having a unique identifier to differentiateeach label 400 from other labels, specifically, from the other 9 labelsintended for delivery to the same delivery point. The unique identifiermay also indicate that a label 400 was generated using a smartphone 236and the label broker system described herein.

FIG. 5A is a flowchart depicting an embodiment of a process 500 forrequesting creation of a label. The process 500 begins in block 502, arequest to access the label request system is sent to the label providersystem 220. The request can be from a computer terminal 232, asmartphone 236, an item receptacle 238, or from another source, such asan interface provided by or providing access to the e-commerce merchant226. The request to access the label provider system 220 can come in theform of entering login credentials to a website associated with thepostage provider 222, such as the USPS's website, a website associatedwith the third party provider 224, or by logging into or opening anapplication on the smartphone 236, such as the USPS application, a thirdparty application, or an e-commerce merchant application.

The process 500 then moves to a decision state 504 wherein the processdetermines whether the user request to access the label provider system220 is recognized. If the user is not recognized, the process returns toblock 502, wherein a request can be re-received. if the user isrecognized, that is, if the login credentials are recognized, or thesmartphone running the application is authenticated or recognized, theprocess moves from block 504 to block 506, wherein the request forcreation of a label is received.

The request for creation of a label can comprise a user inputtinginformation related to the item for shipment, such as senderinformation, recipient information, item dimensions, item weight, itemvalue, destination information, and other desired information via theuser interface system 225. This information can be provided to the labelprovider system 220 via the user interface system 225. In someembodiments, the user interface system 225 can provide label creationrequest communications via label creation request communicationconnection 215 directly to the label provider system 220. In someembodiments, such as where an item is purchased from the e-commercemerchant 226, the label information can be provided by the e-commercemerchant 226, who may have stored item dimensions, item weight, senderinformation, and the like. In some embodiments, the request for creationof a label can occur in the label request system 230. For example, auser may request generation of a label at the item receptacle 238 or atthe mobile terminal 232 while at a retail counter. In this embodiment,the central hub 210 receives the request to create a label from thelabel request system 230 and sends the label creation request to thelabel provider system 220.

The process 500 then moves to block 508, wherein the label is created bythe label provider system 220. The creation of the label can comprisecreating an electronic label, such as an image of a label, .jpeg, .png,.pdf, or other similar file format. In some embodiments, the createdlabel can be a data file, such as a mail.dat file or other type of file.The data file can include the label information used to create thelabel, for example, sender identifier 402, recipient 404,computer-readable indicia 406, postage information 408, trackinginformation (e.g., tracking code 410), and service class information(e.g., service class identifier 412), or any combination of these. Insome embodiments, creating the label can comprise collecting payment forshipping or postage, and postage information, payment indicia, and thelike can be included in the created label. For example, the labelprovider system 220 can debit a user account for payment or postage,requesting payment for postage from the user via the computer terminal232, the smartphone 236, or the item receptacle 238. The payment orpostage information becomes part of the created label.

The process moves to block 510, wherein the created label is received inthe central hub 210. As described above, the created label is anelectronically created label. The created label is received in thecentral hub 210 from the label provider system 220 via the inboundcommunications 217. In some embodiments, the label is sent to thecentral hub 210 and stored in the memory 214 as an image of the label,such as a .jpeg, .png, .gif, .pdf, or the like. In some embodiments, thelabel is sent as information indicative of the label, and can be a datatable or other information that can be populated into label fields bythe central hub 210 or by the label request system 230. The central hub210 generates a label key in response to the label information providedto the central hub 210 from the label provider system 220. The label keycan be a computer-readable code, an alphanumeric string, or the like.The label key is associated with the created label and stored in thememory 214. The central hub 210 can then provide a label key to thelabel provider system 220. In some embodiments, the label providersystem 220 can generate the label key and associate the label key withthe created label.

The process moves to block 512, wherein the created label, that is, theelectronic version of the label, is sent to the system, apparatus, orother entity/device that requested label creation, such as thesmartphone 236. In some embodiments, sending the created label to thedevice requesting creation comprises sending the label key to the devicethat requested label creation as a computer-readable code, an image of acomputer-readable code, and/or in human readable text. In someembodiments, only the label key is sent to the device that requestedlabel creation as a computer-readable code or alphanumeric code. In someembodiments, the label provider system 220 can generate an alphanumericcode and send the alphanumeric code to the entity/device that requestedlabel creation. The alphanumeric code can be associated with the labelkey and/or the electronic version of the label. In some embodiments,where the label creation was requested by a component of the labelrequest system 230 or the user interface system 225 via the labelrequest system 230, the created label, or electronic label, is sent tothe user interface system 225 or the label request system 230. Thecreated label can be sent to a requestor through the same device,platform, or service by which the requestor requested the label. In someembodiments, the requestor can choose how to receive delivery of thelabel. For example, a requestor may request creation of a label via acomputer terminal 233 and may request the electronic label and/or thelabel key to be delivered to the requestor's smartphone 236. The createdlabel and/or the label key can be sent to the requestor in one or moreways. In some embodiments, the created label can be sent to therequestor as an image of the label, such as a .jpeg, .png, .gif, .pdf,or the like. The label key can be sent to the requestor as acomputer-readable code, a token to store on the smartphone 236, orthrough any other desired means. In some embodiments, where the centralhub 210 received the created label as an image, the central hub 210 cansend the created label as an image to the requestor. In someembodiments, the central hub 210 can use label information to fill inlabel fields and create an image of the label, and send the image of thelabel to the requestor.

In some embodiments, the central hub 210 can send the label key, such ascomputer-readable code to the user interface system 225, where the codeis associated with the label information stored in the memory 214. Insome embodiments, the central hub 210 can send the label information tothe requestor in a data file. In some embodiments, the central hub cansend the label key or computer-readable code associated with the labelinformation, or send an image of the label key or computer-readable codesuch computer-readable code to the computer terminal 232, the itemreceptacle 238, or the smartphone 236. The label key can be used by therequestor or user to access the label information, to update labelinformation via an application or website, cancel the label, or requesta refund. The label key can be associated with the created labelinformation. The label key can also comprise additional components, suchas a source identifier which identifies the entity that created thelabel. The label key will be unique for each label created and/orgenerated by the system 200. In some embodiments, the label providersystem 220 sends the label key to the smartphone 236 directly.

The process 500 moves to block 514, where the process ends.

In an exemplary embodiment of a process 500, a user may request labelcreation using the smartphone 236. The creation request may be submittedat a time that is different from the generation of the label. In thisway, the printing of the label can be decoupled from the creation of thelabel. The decoupling may be geographic such that the request to createthe label may be received from a first device at a first location andthe request to generate a physical label may be received later in time,from a different device at a different location. As such the decouplingmay also include temporal decoupling such that generating the physicallabel can be deferred until a point in time after the label is created.

The user can access a website or a specific application configured tocommunicate with the label provider system 220. The user can order anitem to be shipped from the smartphone 236 and be instructed to entershipping details along with the purchase of the item. The applicationcan access a user's payment account information, which can be stored onthe smartphone 236 or in a remote memory. The user requests the labelcreation for the purchased item from the smartphone 236, which sends thelabel creation request via the label request communication connection215 to the label provider system 220.

The label provider system 220 creates the electronic label and sends alabel key, such as a computer-readable code (QR code, barcode, and thelike) or an alphanumeric string to the smartphone 236. In someembodiments, the label provider system 220 may also receive a locationof the smartphone 236 at the time of purchasing the item. This can beprovided from the GPS system of the smartphone 236, or from otherlocation awareness features of the smartphone 236. The label providersystem 220 can additionally send to the smartphone 236 locations,addresses, and the like, of induction points nearest the user and thesmartphone 236. In some embodiments, the user can request locations ofthe nearest item induction points in the application. The inductionpoints can be places where the created label can be generated, and theitem inducted into the distribution network, such as a retail counter, apost office, an item receptacle 238, or other similar location. In someimplementations, a threshold distance may be provided for a location todefine an area within which a device may generate a physical label. Forexample, if the physical label is to be generated for an item by adelivery agent, it may be desirable to confirm that the delivery agentis proximately located to the sender's location before generating thephysical label. The proximity may be assessed using a thresholddistance, such as a geofence, which may be defined as a systemconfiguration value or specific to the label being generated (e.g.,label broker security requirements, value of item to be inducted, valueof the distribution services authorized by the label, etc.).

In some embodiments, the application will provide induction locationsfor the induction points that are near or within the ZIP code entered bythe user when requesting label creation.

In some embodiments, the user can select an induction point from thelist of locations and request generation of a label at a particularinduction point. This will instruct the selected location to generatethe label, which can then be picked up by the user. In some embodiments,the user can request that the label be generated at a certain time inthe future, or within a time window, when the user expects to be at aninduction point. By so doing, the generated label will not be generatedbut not picked up for a long period of time, and the user can avoidstanding in a line to request label generation.

FIG. 5B is a flowchart depicting an embodiment of a process 550 forrequesting creation of a label via the central hub 210. The process 550begins in block 552, wherein a requests access to the label requestsystem. The request can come from the user interface system, forexample, from the smartphone 236 or the computer 233. The request toaccess the label request system can come in the form of entering logincredentials to a website associated with the distribution network, suchas the USPS's website, or by logging into or opening an application onthe smartphone 236, such as the USPS app.

The process 550 then moves to a decision state 554 wherein the processdetermines whether the request to access the label request system isrecognized. If the user is not recognized, the process returns to block552, wherein a request can be re-received. if the user is recognized,that is, if the login credentials are recognized, or the smartphonerunning the application is authenticated or recognized, the processmoves from block 554 to block 556, wherein the request for creation of alabel is received in the user interface system 225. The requests forlabel creation can occur in an application running on the smartphone 236or as a website on the computer terminal 233.

In some embodiments, the website or application can have access toinformation in the user's smartphone 236. For example, the applicationmay have access to the contacts and/or images on the smartphone 236 andmay have access to many other areas of the device. To identify arecipient for the item to be shipped or sent, a smartphone user couldsimply click or tap on a contact listing in the smartphone 236 and theapplication can pull the contact information, including address, phone,etc., and incorporate that information into the label request forincorporation into the label.

The user can send or swipe the contact to the label provider system 220via label creation request transmitted via the label requestcommunication connection 215 or another communication connection. Thelabel provider system then then formats and standardizes the address orname and address for use on the label. The label provider system 220 canalso lookup the address for zip code correction and zip+4 or zip+9inclusion on the label. The label provider system 220 also has access toan address database to see if the address or name and address has aforwarding address. If there is a forwarding address stored in thedatabase, the label provider system 220 creates the label using theupdated or forwarding address. These corrections can automatically bedone so that the proper forwarding address is used with the label. If aforwarding address or new address is identified, the application orwebsite may also prompt the device to request that the user confirm theuser wishes the forwarded address.

In some embodiments, the user can provide a photograph of an item, or alocation or a person to whom the item will be sent. The label providersystem 220 can access a USPS database, such as the household addressdatabase wherein the photo or image of a recipient or deliverydestination may be stored. The label provider system 220 can query ahousehold database using the provided image to find a match, orcorresponding photograph and delivery point details, such as an addressand name for inclusion on the label. The household database can besimilar to that described in U.S. application Ser. No. 15/281,615, filedSep. 30, 2016, the entire contents of which are hereby incorporated byreference.

In some embodiments, the image provided to the website or applicationcan be a photo of another package or piece of mail with a name andaddress displayed. The label provider system 220, or the website orapplication, using another system, can process the image and extract thename and address for inclusion on the label.

In some embodiments, the image can be a unique image, such as a sunset,a landscape, a face or picture of addressee, a drawing, a handmade item,or the like. The website or application, or a connected system can thenprocess the image to see if there is a match between the provided imageand an identical or corresponding image and associated name/address oraddress in a household database maintained by the distribution network.The distribution may utilize anonymous addresses or vanity addressesassociated with physical delivery points or addresses. For example, thewebsite or application, or another computer system, including the labelprovider system 220, or one to which the label provider system 220 isattached, can perform image recognition to identify a recipient based ona provided photograph of an intended recipient for the item. Aphotograph of the recipient can be stored in the household database, andthe website or application can analyze the provided image, such as usingfacial recognition software, to identify the recipient. The recipientwill have a delivery point associated with him or her which can be usedin label creation.

The unique images described here can be entered and populated into thedatabase by individuals or potential recipients who wish to be able toreceive items based on an image, or by senders or third parties simplyby logging on to usps.com and uploading the image to the householddatabase, which is in communication with the website, application,and/or the label provider system 220. For example, a person who wishesto keep his or her address anonymous, can upload an image to thehousehold database, and provide a name/address or address when prompted.The image is then associated in the household database with the addressand can be used for addressing by anyone having the image and providingthe image to the website or application. In some cases, like faces,photos of people, landscapes or the like the website or application, orthe label provider system 220 may process the image to obtain an addressby calling out to another connected database, or a third party databasefor matching. Where a user wishes to keep an address or otherinformation anonymous or private, the website or application does notprovide the address or other information to the website or applicationand does not provide a human readable address on the label, but providesonly a computer-readable address, or code indicating the delivery pointor address on the label, when created and generated.

In some embodiments, the processing of the image can determine whetherthere is any delivery point information in the image itself or anymetadata embedded with the image file. In some embodiments, the imagemay be an image taken inside or near a house, business, school, or otherlocation. The image can have a geo-coordinate associated with thelocation. The geo-coordinates can be matched in a delivery pointdatabase to which the website, application, and/or the label providersystem 220 have access. The geo-coordinates are converted to an addressor a computer-readable code encoding the delivery point, and is sent tothe website or application for verification by the user. In certaincircumstances for privacy or from addressees request the name may not beincluded in the verification request. If the addressee prefers not tohave any verification sent when using this method, the web site orapplication may not send any address back to the smartphone 236 or cansimply send a message saying no match found.

The website or application can send a confirmation prompt to thesmartphone 236 so that the user can verify the address identified fromthe household database which is to be included with the label. If theuser confirms the address, the website or application sends averification response to the label provider system 220 to include theaddress with creation of the label.

In some embodiments, the user requesting creation of a label can clickon a contact record or entry, a cell phone number, email address,twitter handle, customer or e-commerce merchant name or the like withinthe user's smartphone 236. The information is then sent to the websiteor application, the label provider system 220, or the connectedhousehold database, and the household database can match the cell phonenumber, email address, twitter handle, customer or e-commerce merchantname or the like to an associated name/address stored in the householddatabase. In some embodiments, the website or application sends back astealth, anonymous, or vanity address to the label provider system 220for verification/confirmation. The website or application also sends thestealth, anonymous, or vanity address, or a computer-readable codeindicative of the intended recipients name and address, to the labelprovider system 220 for inclusion on the label. These stealth oranonymous addresses include a generic descriptor such as “addressee,” acity and state but leave off the specific name and address. These labelscan be created, generated, and then placed on the item. When the itemprocessing equipment within the distribution network, such as the USPS,reads the label, the USPS systems read the computer-readable code on thelabel, and use the code to determine the destination for the item.

In the case of an e-commerce seller/buyer, twitter handle or the like,the website or application, or connected systems, may contact thee-commerce system, Twitter or other databases for the addressinformation corresponding to the provided seller/buyer name, twitterhandle, etc. These databases can send back not only the address but alsothe preference for the address like stealth only, no contact, orforwarding info. These processes with the e-commerce system, Twitter,and the like can be opted into by the party who wishes to receive itemsbased on the e-commerce system, Twitter, etc., handle or user name.

The website or application can also collect identifiers of thesmartphone 236 being used to perform the label creation request, such asan ESN, MEID, IMEI, chip id or cell number to include in the databaserecord for later verification or authentication. An identifier for thesmartphone 236, or an association with the smartphone 236 can be storedin the label record in the hub 210 for use in subsequent labelgeneration.

The request for creation of a label can comprise a user inputtinginformation related to the item for shipment, such as senderinformation, recipient information, item dimensions, item weight, itemvalue, destination information, and other desired information.

The process 550 then moves to block 558, wherein the request for labelcreation is sent to a label provider system 220 via the label requestcommunication connection 215. In some embodiments, the request for labelcreation from the user can indicate which component or label provider ofthe label provider system 220 is to be used for creation of the label.In some embodiments, label provider system 220 can triage or distributerequests for label creation to postage provider 222 and the third partyprovider 224 according to a specified pattern, such as alternating, oraccording to geographic location of the label requester. In someembodiments, the label requestor can be a retailer, a store, afulfillment warehouse, and the like, which may have an account with thedistribution network, and may be affiliated with an e-commerce merchant226. In this case, requests for labels from commercial entities can besent to the e-commerce merchant 226. In some embodiments, the labelrequester and the e-commerce merchant 226 can be the same entity. Insome embodiments, the label creation communication can be routed to thecentral hub 210, which can then provide the label creation request tothe label provider system 220. In some embodiments, where the e-commercemerchant 226 requests creation of the label, the e-commerce merchant 226may request the label on behalf of a recipient. The e-commerce merchant226 may request label creation on behalf of a user, such as an itemsender or item provider. For example, the e-commerce merchant 226 mayrequest an electronic label on behalf of a user where the e-commercemerchant 226 has facilitated a transaction between a sender and arecipient. The e-commerce merchant 226 can receive the label key fromthe label provider system 220, and can send the label key, the computerreadable code, alphanumeric code, and the like to the user, which theuser can then use to request generation of a physical label as describedherein.

The process moves to block 560, wherein the created label is received.As described above, the created label can be an electronically createdlabel. The creation of the electronic label can include debiting a useraccount for payment or postage, requesting payment for postage from theuser via the computer terminal 232 or the smartphone 236. The payment orpostage information becomes part of the created label. The createdlabel, or the electronic version of the label is sent by the labelprovider system 220 to the central hub 210. As described above, thecreated label can be received as a virtual label, such as an image of alabel, .jpeg, .png, .pdf, or other similar file format. In such case theimage of the label is received and stored in the memory 214. In someembodiments, the created label can be a data file, such as a mail.datfile or other type of file which includes the label information used tocreate the label, for example, sender identifier 402, recipient 404,computer-readable indicia 406, postage information 408, trackinginformation (e.g., tracking code 410), and service class information(e.g., service class identifier 412), or any combination of these. Thedata file is stored in the memory 214. The label provider system 220also sends a label key, such as a computer-readable code, analphanumeric string, or the like, along with the created label or labelinformation to the central hub 210. The label key is associated with thecreated label and stored in the memory 214.

In some embodiments, when a label is created, information regarding theuser or requestor can be collected by the central hub 210. For example,where the requestor uses a smartphone 236 to request label creation, thelocation, such as the GPS coordinates of the smartphone 236, can berecorded and stored. Knowing the location of the smartphone 236requesting the label can be provided to the distribution network. Thelocation information can be automatically sent to a carrier who will bealerted via the mobile delivery device 234 that a label has beenrequested and instructing the carrier to proceed to the location of thesmartphone where the label was requested to pick up the item. In someembodiments, the location of the smartphone 236 can be stored andcompared to a known address of the requestor.

The process moves to block 562, wherein the created label is sent to theuser requesting the label, such as the user interface system 225. Thecreated label can be sent to a requestor through the same device,platform, or service by which the requestor requested the label. In someembodiments, the requestor can choose how to receive delivery of thelabel. For example, a requestor may request a label via a computerterminal 233 and may request the label be delivered to the requestor'ssmartphone 236. The created label can be sent to the requestor in one ormore ways. In some embodiments, the label can be sent to the requestoras an image of the label, such as a .jpeg, .png, .gif, .pdf, or thelike.

In some embodiments, the label provider system 220 sends a label key,such as computer-readable code to the requestor, which is associatedwith the created label and the label information stored in the memory214. In some embodiments, the label provider system 220 can send thelabel information to the requestor in a data file. In some embodiments,the label provider system 220 can send the label key orcomputer-readable code associated with the label information, or send animage of the label key or computer-readable code such computer-readablecode to the computer terminal 233 or the smartphone 236. The label keycan be used by the requestor or user to access the label information, toupdate label information via an application or website, cancel thelabel, or request a refund. The label key can be associated with thecreated label information. The label key can also comprise additionalcomponents, such as a source identifier which identifies the entity thatcreated the label. The label key will be unique for each label createdand/or generated by the system 200.

The process 550 moves to block 564, where the process ends.

Although processes 500 and 550 are provided as two examples of processesfor requesting a label, the processes are exemplary only, and processeswhich mix, combine, or select the descriptions, elements, of one or moresteps of processes 500 and 550 are explicitly contemplated by thepresent disclosure.

FIG. 6 depicts a flow chart of a process 600 for requesting generationof a label. The process 600 begins at block 602 wherein a request forlabel generation is received at the label request system 230. Therequest for label generation can occur at the item receptacle 238, or ata facility associated with the distribution network, such as at acomputer terminal 232, which may be located at a post office. Therequest for label generation can be made by a user interacting with thelabel request system 230.

The requestor of the generated label can be the entity that requestedcreation of the label as described with regard to FIG. 5A or 5B. Thegeneration requestor can approach the item receptacle 238 and select anoption on the user interface for generation of a label. In someembodiments, the user can scan a label key located on the smartphone 236at a scanner on the item receptacle 238, or at the computer terminal232. The generation requestor can bring the item to be sent to the itemreceptacle 238, ready to receive the generated label.

The process 600 moves to block 604 wherein label generation informationis received. This label information can be received from the generationrequestor via the user interface 120 on the item receptacle 100 (or to asimilar component on item receptacle 238). For example, the userinterface 120 can request the user input label generation informationand may prompt the user to scan a computer-readable code, the label key,or the image of the label via the sensor 124. The requestor can navigateon the smartphone 236 to the received label information and hold thesmartphone 236 in proximity to the sensor 124. In some embodiments, therequestor displays the label key or computer-readable code received inresponse to the request for label creation on the smartphone 236, andholds the smartphone 236 in proximity to the sensor 124. The sensor 124reads the computer-readable code from the smartphone 236 via opticalrecognition, a barcode scanning, or the like.

In some embodiments, the requestor displays on the smartphone 236 theimage of the label received during the request for label creation andholds the smartphone 236 in proximity to the sensor 124, wherein it isread, scanned, imaged, or otherwise input. In some embodiments, wherethe image of the created label is displayed, the sensor 124 can read thecomputer-readable indicia 406 on the image of the label.

In some embodiments, the processes described above with regard to FIGS.5A and 5B, and FIG. 6, can be performed while a user is physicallypresent at the item receptacle 238. For example, the user can connecthis or her smartphone 236 to the item receptacle 238 via a wirelessprotocol, such as Bluetooth, or another desired protocol and communicatewith the system 200 via the item receptacle 238. The item receptacle 238can be in communication with the label provider system 220 and canprovide and receive information from the label provider system 220. Insome embodiments, a user can bring an item to the item receptacle 238and access the label provider system 220 via the item receptacle. Theuser can provide the information described elsewhere herein and requestcreation and generation of the item at the item receptacle 238.

A user may interact with the item receptacle 238 using voice commands toinstruct the item receptacle 238 regarding generating the label. In thiscase the item receptacle 238 can have a microphone connected to speechrecognition software. The voice commands can be provided with thecomputer-readable code, and/or can be provided on the item receptacle.The user can speak a code, provided by the label provider system 220 andthen to the smartphone 236, to the item receptacle 238, and the itemreceptacle

In some embodiments, the user can be present at the item receptacle 238and input a code or identifier on the item receptacle into the user'ssmartphone 236, which tells the hub 210 and the label provider system220 where the user is, and where the label should be generated. Theapplication on the smartphone 236 can communicate with components of thesystem 200 through the item receptacle 238 and/or through wirelesscommunication methods, such as Wi-Fi, cellular, LTE, and the like.

In some embodiments, the user can connect to the item receptacle using apairing protocol, such as Bluetooth, NFC, or the like. The softwareapplication on the smartphone 236 can be configured to provide a token,or security identifier to the item receptacle via the pairing protocolto confirm the identity of the smartphone 236 as the phone whichrequested label creation. The application can also automaticallytransmit the label key via the pairing connection to the item receptacle238. The item receptacle 238 uses the label key to identify which labelis to be generated and confirm the identity of the smartphone 236 thatrequested creation of that label. When the pairing is established, theidentity confirmed, and the label key provided, the item receptacle 238can automatically provide the label to the user. In this way, the userdoes not need to physically interact with the item receptacle 238.

In some embodiments, the item receptacle 238 can be continuously or atintervals, scanning for nearby smart devices. When a smart device isdetected, the item receptacle 238 can access a database of labelsprovided and smartphone identifiers associated therewith. When the itemreceptacle identifies a match, the item receptacle can send anotification to the smartphone 236 that the item receptacle is nearbyand that there is a label to generate. In some embodiments, thenotification can include an interaction feature to receive aninstruction to generate the label.

The process 600 moves to decision state 606 wherein it is determined ifthe requested label is valid. To determine if the label generationinformation is valid, the item receptacle 100 transmits the receivedgeneration information to the central hub 210, where the central hub 210queries the memory 214 to determine whether label informationcorresponding to the information received via the request is present inthe memory 214. The memory 214 can also store information related to thetime and date of creation of the label, whether the label has beengenerated (printed) previously, the date and time of generation of thelabel, whether the label has been used before, or any other desiredinformation.

With information received from memory 214, the central hub 210determines whether the request for label generation has occurred withina specified time period from the request for creation of the label. Insome embodiments, the created label may be valid for a day, a week, amonth, two months, six months, a year, or any other desired time period.If the request for generation of the label occurs after the specifiedtime period, the process moves to block 606 and displays a message thatthe label is not valid.

In some embodiments, the central hub 210 can determine that therequested label has already been generated previously, or upon a priorrequest. If the label has previously been requested, the central hub 210can return a message that the label is not valid, or cannot begenerated, as in block 608. In some embodiments, the central hub 210 candetermine, via interfaces to other systems of the distribution networknot described here, that the label has already been scanned on an itemin the distribution network and can determine the label cannot begenerated. In some embodiments, the central hub 210 can determine thatpostage has not yet been paid for a created label, and the userinterface 120 can request a payment be made before the label can begenerated. Once payment has been received, for example, via paymentdevice 126, the process can continue.

If the requested label is valid, or can be generated, the process 600moves to block 610, wherein the label is printed via the printer 128using the label information stored in the memory 214. The generatedlabel can be a self-adhesive label which the requestor can affix to theitem.

The process moves to decision state 612, wherein it is determinedwhether the item has been deposited into the item receptacle 100. Arequestor generally will take the generated label and affix thegenerated to the label. The item with the affixed label is thendeposited in the item receptacle 100 to induct the item into thedistribution network. The item receptacle 100 can detect whether theitem has been deposited via the internal image capture device 330, thescale 335, a sensor on the rotating drum of the item receptacle, orother detection method. If the item is not detected, the process movesto block 614, wherein the user interface 120 displays a prompt todeposit the item in the item receptacle 100. The process then ends inblock 616.

If the item has been detected in the item receptacle 100, the process600 moves to block 616, wherein the process ends. In some embodiments,the printer 128 can provide a receipt of item deposit.

FIG. 7 is a flow chart depicting a process 700 for generating a labelusing a mobile delivery device, such as mobile delivery device 234.Process 700 begins where a created label is sent to a user or labelrequestor. This process can be similar to process 500, wherein a requestfor label generation occurs and a request for label creation isreceived, and a label is created and sent to the user or requestor.

The process 700 then moves to block 704, wherein a request for labelgeneration is received in a mobile delivery device. In some embodiments,this occurs as a delivery resource, such as a carrier, receives anotification on the mobile delivery device 234 that a customer, sender,requestor, user, or other entity has an item for pickup, which is to bedelivered via the distribution network. This notification is generatedand send to the carrier in response to the request for label creationand the created label being sent to a user. The central hub 210 can senda notification to the delivery device 234 at the request of therequestor or user, or automatically send the notification upon creationof the label, sending the created label information, or at another timeas determined by the central hub 210.

The process 700 moves to block 706, wherein the label generationinformation is received in the mobile delivery device 234. When thecarrier is at a location of a user having the item for pickup, thecarrier, using the mobile delivery device 234 scans or reads the createdlabel information sent to the user in block 702. The mobile deliverydevice 234 can scan or read the created label information and/or thelabel key from the user's smartphone 236 or computing terminal 232, orfrom a paper having the label information, label key, or acomputer-readable code, thereon. In some embodiments, the carrier caninput an alphanumeric code into the mobile delivery device, where thealphanumeric code was provided to the user upon the request for creationof the label. The mobile delivery device can send the inputtedalphanumeric code to the central hub 210 to request label generation ofthe label associated with the alphanumeric code.

When the label information is received, the process moves to decisionstate 708, wherein it is determined whether the requested label isvalid. Determining whether the label is valid in decision state 708 canbe similar to the process for determining whether the label is valid indecision state 606 of process 600. In some embodiments, the process ofdetermining whether the label is valid can occur upon scanning the labelgeneration information, via the wireless communication features of themobile delivery device 234. The mobile delivery device 234 sends therequested label information to the central hub 210, and the central hubdetermines whether the requested label is valid, as described elsewhereherein. In some embodiments, the carrier receives the item fordistribution and places the distribution item in the truck or on avehicle. The carrier also connects the mobile delivery device to thevehicle, wherein the label generation information is retrieved from themobile delivery device 234 and communicated to the central hub 210 via awireless communication mechanism on the carrier's vehicle, wherein thecentral hub 210 determines whether the requested label is valid, asdescribed elsewhere herein.

If the label is not valid, the process moves to block 710, wherein amessage is displayed that the label is not valid. If the label is notvalid, a notification can be automatically sent to the user orrequestor, for example, to the smartphone 236. In some embodiments, thenotification can include a request for additional information, postage,or other information to cure the problem with the label generationinformation. In some embodiments, the notification can be an invitationto create a new label, and the process of label creation can occur tocreate a new label.

If the label is determined to be valid, the process 700 moves to block712, wherein the label is generated. In some embodiments, the carriermay have a mobile printing device, or the mobile delivery device 234 cancomprise a printing device for generating the physical labels. When thecarrier scans the requested label information and validity of the labelis confirmed, the mobile printer or mobile delivery device canautomatically, or upon prompt from the carrier, generate the physicallabel. The carrier or user can affix the label to the item, and thecarrier takes the item for delivery.

In some embodiments, the carrier's vehicle can have a printer thereon.Where the mobile delivery device 234 receives confirmation that therequested label is valid, the carrier can take the item to the vehicle.In some embodiments, mobile delivery device 234 can send a command,either automatically or upon a prompt from the carrier, to the printeron the carrier's vehicle to generate the physical label when the mobiledelivery device 234 receives notification of the requested label beingvalid. When the carrier returns to the vehicle from picking up the item,the label is on the printer. In some embodiments, the mobile deliverydevice 234 is docked in a dock on the vehicle. When the mobile deliverydevice 234 is docked, the dock, in communication with the vehicleprinter, can instruct the vehicle printer to print the physical label.

In some embodiments, a carrier may wish to print the labels for itemsbefore the carrier leaves a distribution facility. The carrier canaccess the central hub 210 via an administrative interface or via themobile delivery device 234, and request generation of labels that havebeen previously created by requestors, for items that will be availablefor pickup along the carrier's route. For example, before leaving for adelivery route, the carrier can request that any labels for items to bepicked up along the carrier's route be generated at the distributionfacility. The carrier can retrieve the group of labels and take them onthe delivery route. As items are picked up, the carrier can attach theappropriate label to the item.

In some embodiments, the central hub 210 can automatically initiate theprinting of labels for items to be picked up along a specific route, andcan send a notification to the carrier, for example, via the mobiledelivery device 234, to pick up the labels for the carrier's deliveryroute. This can be automated to occur daily at a given time, at aspecified interval, or at any other desired time.

The process 700 moves to block 714, wherein the label is affixed to theitem. This can be done by the user, such as when the carrier has amobile printer, or can be done by the carrier. The item is loaded on thevehicle and is transported to a facility in the distribution network fordelivery to the intended recipient of the item.

The process 700 then ends in block 716.

FIG. 8 is an exemplary process flow diagram showing data flows betweenentities in the system of FIG. 2. FIG. 8 depicts how components of thesystem 200 interact and how data can flow within the system 200.

FIG. 9 is an exemplary process flow diagram showing data flows betweenentities of FIG. 2 for label generation. FIG. 9 depicts alternate orparallel data flows based on a user's chosen mode of label generation.Specifically, FIG. 9 depicts data flows for label information where auser selects to have a label generated at a self-service labeling kiosk,such as at an item receptacle 100, at a retail counter, such as at aUSPS facility (which can use a computer terminal 232), label generationby a carrier, such as using the mobile delivery device 234.

Several examples of using the systems and methods described in thepresent application will now be discussed. One use case includes ashipper, such as a shipper or seller on an auction or seller website,but who does not have or does not wish to print labels at home forshipping can use the system 200. The seller can make a sale in an onlinemarketplace. The seller can then request label creation via a website orapplication as described herein. Then, the seller, at his or her ownconvenience can go to the item receptacle 100 and request the label begenerated using a code on his or her smartphone 236 and deposit the itemin the item receptacle. Or the seller can request the delivery carrierto scan the code and print the label and take the item.

Another example is a shopper who buys an item and wants to send the itemto another as a gift. The shopper buys the item and accesses theapplication via his or her smartphone 236. The shopper creates the labeland receives a code for label generation. The application can tell theshopper where the nearest item receptacle 100 using the geo-coordinatesof the smartphone 236 to locate the shopper. The application can providethe location of all the item receptacles within a certain radius ordistance, or near a zip code or in any other desired location. Theapplication can then provide directions to nearest item receptacle 100,or to a selected item receptacle. The shopper then goes to the itemreceptacle 100, scans the code, and the item receptacle generates thelabel, which the shopper attaches to the item. The shopper then depositsthe item in the item receptacle 100.

In another example, a user can start a shipment from a home computerusing a website or other software application or portal. The user maynot have a scale, and so cannot input the weight or pay for postage,etc. The user can request creation of the label via the website,application, or portal. The user then goes to the item receptacle 100(238), which has a scale. The user scans the code for the label receivedfrom the website, and then weighs the item on the scale. The itemreceptacle determines the weight and then calculates postage. The usercan pay the postage at the item receptacle 100 or can have the amountdebited or charged to a credit card associated with the user's account.The label is then generated, and the user attaches the label to the itemand deposits the item in the item receptacle.

The following tables show some of the features and functionality of thesystem 200 and communication between components of the system 200.

TABLE 1 THEME: Access Control AS A . . . I WANT TO . . . SO THAT . . .Admin Define authorized label providers Access is restricted to known,authorized users Admin Define authorized label requestors Access isrestricted to known, authorized users Admin Store credentials to sendrequests to Outbound requests will be label providers accepted LabelBroker Only allow labels to be provided from Security is maintainedavoid authorized label providers with an attacks and preventing fraudauthorized user id and password. Label Broker Only allow labels to berequested Security is maintained avoid from authorized label requestorsas attacks and preventing fraud using user id and password Label BrokerUse customer registration for user id Customer registration is thesingle and password credentials. source for access control Label BrokerStore an audit log of requests The admin can audit any changes (inboundand outbound) including the to labels following data: date and time;requesting user id; label provider, request made, label identifier,success or failure, and if a failure, the reason code

TABLE 2 THEME: General Administration AS A . . . I WANT TO . . . SO THAT. . . Admin Store a source identifier, which, The provider can beidentified from when included in a key will identify the key alone thelabel provider Admin Define a number of days at which The label brokerwill not have to labels will permanently expire keep labels foreverAdmin Define the date of any price change The label broker will notprint a and the mail classes affected label which could potentially beshort paid Admin Set date and time “triggers” to run Batch processdefined below can the batch processes (defined below) be runautomatically Admin Be able to manually start batch The system canrecover from processes outages which may have prevented batch processesfrom running

TABLE 3 THEME: Store a new label AS A . . . I WANT TO . . . SO THAT . .. Label Send data, that is a description of The label provider willProvider the elements that make up a label have label details in a suchas mail class, delivery format that can be address, etc., to the labelbroker queried, tested and reported Label Send an image of the label tothe The image can be printed Provider label broker Label Receiveconfirmation that the label The label provider can Provider data andimage were successfully resolve any issues to stored or a reason codeindicating provide a new label why it wasn't Label Receive a uniquelabel identifier The label can be Provider that will uniquely identify areferenced by that label's data and image identifier for update, void,reporting, etc. Label Validate required elements are The validationsdefined Broker provided in the label data such as in subsequent storiesmay ship data, mail class, and any other be properly processed elementsidentified as required by other stories Label Validate label ship dateto be within Expired labels, labels too Broker a range from today's dateto either far in the future or labels its permanent expiry date or aprice that cross a price change change for the label's mail class willnot be accepted Label Create a unique label identifier to So that labelscan be Broker identify the new label uniquely identified for printing,update, reporting, etc. Label Store a label which passes The label isavailable Broker validations in available status for printing LabelInform the label provider of a The label provider can act Broker successor failure and provide the accordingly label identifier

TABLE 4 THEME: Void a label AS A . . . I WANT TO . . . SO THAT . . .Label Request that a label be Labels which have been voided Providermade unavailable for or for which a refund has been print requestedcannot be printed Label Validate that the label To determine if an errorhas Broker identifier exists occurred Label Validate that the labelLabels can only be voided Broker identifier belongs to the by theoriginal requestor requesting label provider Label Validate that thelabel Printed labels cannot Broker identifier has not already be voidedbeen printed Label Mark the label as voided The label cannot be printedBroker Label Inform the label provider The label provider can act Brokerof a success or failure accordingly

TABLE 5 THEME: Request label status AS A . . . I WANT TO . . . SOTHAT... Label Request the status of a Label intermediaries such asProvider label marketplaces can be informed Label Validate that thelabel Labels status is only shared Broker identifier belongs to the withthe original requestor requesting label provider Label Inform therequestor of The label provider can act Broker label status or requestaccordingly failure

TABLE 6 THEME: Update a label AS A . . . I WANT TO . . . SO THAT . . .Label Provide new label data and a new Label ship dates can be Providerimage to update a label changed Label Insure the label is not in“Printed,” Only valid labels are Broker “Voided” or “Permanently updatedExpired” status Label Validate that the label identifier Labels can onlybe Broker belongs to the requesting label voided by the originalprovider requestor Label Validate required elements are The validationsdefined in Broker provided in the label data such as subsequent storiesmay be ship data, mail class, and any other properly processed elementsidentified as required by other stories Label Validate label ship dateto be within a Expired labels, labels too Broker range from today's dateto either its far in the future or labels permanent expiry date or aprice that cross a price change change for the label's mail class willnot be updated Label Store the new label data and image The updatedlabel is now Broker available for printing Label Inform the requestor oflabel status The label provider can act Broker or request failureaccordingly

TABLE 7 THEME: Print a label AS A . . . I WANT TO . . . SO THAT . . .Label Request a label by label identifier The label can be Requestorprinted for the user Label Provide the label image to the printer Therequestor can Broker if the label identifier exists in either print thelabel Available or Printed status Label Provide a reason code to the Sothe requestor can Broker requestor if the label does not exist informthe user or exists in a non-printable status Label Inform the labelbroker of a So the status can be Requestor successful print or printfailure updated Label Update the label to Printed status So the statusreflects Broker when the print is successful the current state LabelUpdate the label to Print Failure So the status reflects Broker statuswhen the print is unsuccessful the current state Label Send a printnotification (success or The label provider can Broker failure) to thelabel provider act accordingly

TABLE 8 THEME: Reporting AS A . . . I WANT TO . . . SO THAT . . . AdminBe able to query number of labels A snapshot of the system by statususage is available Admin Be able to view request log Problem diagnosiscan be performed Admin Be able to view status for a An individual labelparticular label identifier printing problem can be diagnosed Admin Beable to query request history by Problem diagnosis can any parameter orcombination of be performed parameters in the request log (e.g.: allrequests for a certain date or all requests from a particular user on acertain date) Admin Be able to view available storage Capacity planningcan and any storage alerts (storage be performed greater than threshold)Admin Be able to view current (latest) Problem diagnosis can responsetime by request and be performed response time history

TABLE 9 THEME: Batch Process to automatically expire labels AS A . . . IWANT TO . . . SO THAT . . . Label Mark labels in Available status who'sLabels are not Broker ship date is more than the permanent stored asavailable expiry number of days prior to today's indefinitely date as“Permanently Expired” Label Mark Available labels “Permanently Labelsthat may have Broker Expired” if today = a price change incorrectpostage due to and their mail class is affected. the price change arenot available for printing Label Mark Available labels who's originalUsers cannot print labels Broker ship date is less than the permanentwhere the ship date on expiry number of days prior to today's the labelis not current date as “Expired” Label Inform the label provider with anThe label provider has Broker outbound call of status changes the optionto send a label with a current date

The labelling and induction features described herein allow the shiftingof the time and the location of label generation from the time andlocation of requesting the label. This can be useful to allow arequested label to be physically produced at a variety of locations and,in some instances, by a party that did not directly request the labelsuch as a postal carrier.

In some embodiments, the user may provide an identifier at a retaillocation. The identifier may be provided through a physical medium(e.g., printed paper) or through a digital medium (e.g., scannable codedisplayed on a smartphone, NFC communications, etc.) which can be inputat the retail location. A retail clerk may scan the barcode or key inthe human readable code and provide the user with a physical label. Ifthe user has their package with them it can be tendered immediatelyalong with an acceptance scan and receipt. The retail systems mayinclude features (e.g., interfaces) to accept a label ID by eitherscanning a code or manually entering the ID. The retail system may thentransmit a request for the label to the central hub who may, in turn,provide the label. If the label is found and available for printing theretail system may activate a printer to produce a physical label. Oncesuccessfully produced, the retail system may call the central hub toupdate the label status to printed.

In some embodiments, the user may request at home labeled induction ofan item. For example, a label provider or distribution network providerassociated with the label (e.g., USPS) may include an option for at homelabeling when creating a label or after label creation if the labelstatus is not “printed” or “expired.” The label may be delivered to theuser with their regular mail delivery on the next business day or thebusiness day of their choosing. In some implementations, the user mayrequest at home label delivery by scheduling a package pickup. Thelabels for the scheduled date may be preprinted and provided to adelivery agent responsible delivery to the user's location. In someimplementations, the labels may be stored on a handheld communicationdevice associated with the delivery agent. In such implementations thehandheld device may communicate with a mobile printer to produce thephysical label. As discussed, the printing may be based on proximity ofthe handheld device to a location which requested at home labeldelivery.

In some implementations, a third-party may request the label on behalfof a user. For example, if a retailer wishes to provide shipping for anitem to be returned by a user, the retailer may request the label andprovide the label ID to the user who is returning the item. In suchinstances, the user may print the label at a retail location orinduction kiosk by presenting the label ID. In some instances, the usermay wish to print the label on a personal printer. An interface may beprovided to receive the label ID and initiate production of the physicallabel.

FIG. 10 is an example interface for requesting production of a physicallabel. The interface 1000 may be a graphical user interface presented ona communication device of the user or at a self-service kiosk, aninduction unit, or other induction communication device. The interface1000 includes input elements to receive the label ID and otherinformation to confirm the label (e.g., return address ZIP code). Theinterface 1000 also includes selection element to allow the user toselect which form of label induction to use. As shown in FIG. 10, theuser may select to print or download in two different formats or requestan at home label delivery. The interface 1000 may include additionalinput elements to collect information corresponding to a selectedinduction method (e.g., name, street address, and delivery date for athome label delivery).

Embodiments may include one or more of the following features tofacilitate labeled induction. While the embodiments are described asnetwork-based service calls, it will be appreciated that alternateembodiments such as thick-client applications or purpose builtcommunication devices may be used.

To provide security, the system 200 may require 2-way mutual securesocket layer (SSL) authentication. For example, users may be required tohave an SSL client-id certificate that is issued by a certificateauthority. Authorized users may also be required to have theircertificates pre-registered with the system.

A label provider (e.g., label broker) may need to satisfy one or morerequirements prior to making use of the network-based services offeredthrough the system. One requirement may be registration of an SSLcertificate. Registration may include obtaining a valid SSL clientcertificate issued by the certificate authority and registration of thesubject common name (CN) of the certificate within the system. Anychange in the subject CN may result in an unrecognized certificate.Another requirement may be certification of the label provider. Thecertification may be an automated, manual, or hybrid process by whichthe label provider is assessed for compliance with the communicationsfor requesting and managing labels. After completion of thecertification process a provider may have access to the system forlabeled item induction.

The labeled item induction may include a variety of steps to store a newlabel, request status for one or more labels, change or validate statusof a label, etc.

A store label service may allow providers to save a label image and theassociated label data under a unique label ID. The label ID is theunique identifier of a label within the label provider, and can be usedin later label status and print requests. Label IDs may have thepotential of being reused after its associated label is permanentlyexpired and/or purged—no earlier than 3 years after the physical labelcreation date. Table 10 provides example request information that may bereceived from a label provider by the central hub 210. Some values maybe limited to an enumerated set of valid values. The enumerations maycorrespond to existing standards such as the US Postal Service'sShipping Services File Record Version 1.6 Layout (SSF v1.6) which ishereby incorporated by reference in its entirety.

TABLE 10 Corresponding Shipping Services File Fields Data Format LengthRequired Details (SSF) field paymentType Numeric 2 Y Code for an SSF:Method of acceptable Payment payment type such as those identified inSSF v1.6 mailClass Alphanumeric 2 Y Code for mail SSF: Class of Mailclass such as those identified in SSF v1.6 accountNumber Alphanumeric<=20 Y Numbers 0-9 SSF: Payment Account allowed Number (paymentType =Ex. 0123456789 01, 03) SSF: Meter Serial Number (paymentType = 04, 05,06) accountZipCode Numeric 5 Y Numbers 0-9 SSF: Post Office ZIP allowedCode Ex. 01234 shipDate Numeric 8 Y Format: SSF: Date of MailingYYYYMMDD Ship Date must be current or future date. Future date must notexceed max allowable ship date. trackingNumber Numeric <=34 Y aka IMpbSSF: Tracking Number Numbers 0-9 allowed recipientName Alphanumeric <=48N If input exceeds SSF: Recipient Name length limit, it will betruncated and then saved recipientAddress1 Alphanumeric <=48 N InputsSSF: Destination exceeding Delivery Address length limit, it will betruncated and then saved recipientAddress2 Alphanumeric <=48 N If inputexceeds SSF: Destination length li (e.g., Delivery Address mit, it willbe truncated and then saved recipientCity Alphanumeric <=48 N If inputexceeds SSF: Destination City length limit, it will be truncated andthen saved recipientState Alphanumeric 2 N Must be a valid SSF:Destination State state abbreviation recipientZip Alphanumeric 5 Y SSF:Destination ZIP Code recipientZip4 Alphanumeric 4 N SSF: DestinationZIP + 4 senderName Alphanumeric <=48 N If input exceeds SSF: Sender Namelength limit, it will be truncated and then saved senderAddress1Alphanumeric <=48 N If input exceeds SSF: Return Address length limit,it will be truncated and then saved senderAddress2 Alphanumeric <=48 NIf input exceeds SSF: Return Address length limit, it will be truncatedand then saved senderCity Alphanumeric <=48 N If input exceeds SSF:Return Address length limit, it City will be truncated and then savedsenderState Alphanumeric 2 N Must be a valid SSF: Return Address stateState abbreviation senderZip Numeric 5 N Numbers 0-9 SSF: Return Addressallowed ZIP Code Ex. 01234 senderZip4 Numeric 4 N SSF: Return AddressZIP Code + 4 masterMid Alphanumeric 6 or 9 Y SSF: Mailer IDserviceTypeCode Alphanumeric 3 Y Code SSF: Service Type specifying aCode service type such as those identified in SSF v1.6 merchantIdAlphanumeric <=30 N SSF: Customer Reference Number 1entryFacilityZipCode Numeric 5 Y SSF: Entry Facility ZIP Code weightNumeric 7 N Format: SSF: Weight NN.NNNN (in lbs.) Range: 0- 99.9999length Numeric 6 N Format: SSF: Length NNN.NN (inches) Range: 0- 999.99width Numeric 6 N Format: SSF: Width NNN.NN (inches) Range: 0- 999.99height Numeric 6 N Format: SSF: Height NNN.NN (inches) Range: 0- 999.99processingCategory Alphanumeric 2 N Code SSF: Processing specifying aCategory processing category such as those identified in SSF v1.6rateIndicator Alphanumeric 2 N Code SSF: Rate Indicator specifying arate indicator such as those identified in SSF v1.6 fileExtensionAlphanumeric 3 or 4 Y Label image file extension (e.g., PDF, JPG, GIF,PNG, etc.) labelImageBase64 Alphanumeric Y Image file as base64 encodedstring

The central hub 210 may provide a response to the request indicating thestatus of the label creation request. Table 11 provides example responseinformation that may be transmitted from the central hub 210 to thelabel provider system 220 r.

TABLE 11 Name Data Format Required Length Details methodName String Y 19e.g. “StoreLabelResponse” labelDataId String Y 10 The Unique ID of theLabel labelStatus String Y  9 See list of acceptable Label Status CodesresponseCode Numeric Y  4 See list of Response Codes responseMessageString N 27 If the value in the responseCode field <> 200 (i.e., therequest failed), then this field will be replaced with thevalidationErrors field validationMessages List N Dependent Contains alist of validation <ValidationMessages> on returned messages, each ofwhich contains validation the response code, response type messages(warning or error), and detail message. It is possible to receive aSuccessful response with Warning messages for minor validation issueswith the input parameters. The request will be processed and saved.However, any Error messages will result in rejection of the Request, anda Failure response will be returned. The request will not be processedand not saved.

The central hub may provide status services to allow providers torequest the status of one or more labels. Status for a single labelstatus may be requested by providing its unique label ID. The label IDmay be an alphanumeric string of a predetermined size or range of sizes(e.g., 8-10 characters). Table 11 provides example response informationthat may be transmitted from the central hub 210 to the label providersystem 220 for a status request.

TABLE 12 Name Data Format Required? Length Details MethodName String Y18  “RequestLabelStatusResponse” ResponseCode Numeric Y 4 See list ofResponse Status Codes ResponseMessage String Y SUCCESS or FAILUREsystemLogId Numeric Y Unique identifier associate to this specific APIcall ValidationMessages List N Dependent on the If the Response Code is200 <ValidationMessage> validationMessages (success), then this will bereturned omitted. If the RequestStatus is not 200 (i.e., the requestfailed), then this will be populated Contains a list of validationmessages, each of which contains the response code, response type(warning or error), and detail message. labelAttributes List N Returns asub object containing <LabelAttributes> LabelId and labelStatus LabelIdAlphanumeric Y 8-10 The Unique ID of the Label LabelStatus String Y 7Label's status

In some implementations, it may be desirable to reduce the amount ofnetwork communications needed to request status for multiple labels. Oneway to improve the efficiency of status requesting for multiple labelsis to provide bulk status request service. The bulk status requestservice allows label providers to request the status of multiple labelsbased on their ship date values. The request may include a two ship datevalues identifying the range of days for which label status will beprovided. To minimize the impact on the central hub 210, the bulkinterface may limit the range to a predetermined number of days (e.g.,10 days). Table 13 provides example response information that may betransmitted from the central hub 210 to the label provider system 220for a status request.

TABLE 13 Name Data Format Required? Length Details MethodName String Y18  “BulkRequestLabelStatusResponse” ResponseCode Numeric Y 4 See listof Response Status Codes ResponseMessage String Y SUCCESS or FAILUREsystemLogId Numeric Y Unique identifier associate to this specific APIcall ValidationMessages List<ValidationMessage> N Dependent If theResponse Code is 200 on the (success), then this will be omitted.validationMessages If the RequestStatus is not 200 (i.e., returned therequest failed), then this will be populated Contains a list ofvalidation messages, each of which contains the response code, responsetype (warning or error), and detail message. labelAttributes List NReturns a sub object containing <LabelAttributes> LabelId andlabelStatus for each label within the requested range. LabelIdAlphanumeric Y 8-10 The Unique ID of the Label LabelStatus String Y 7Label's status

The central hub 210 may include a void label service to allow providersto void a single label by providing its unique label ID. The central hubmay update a disposition status for the specified label and provide aresponse to the label provider system requesting the voiding. Examplesof information that may be included in a response to the label providersystem 220 from the central hub 210 to void a label are shown in Table14.

TABLE 14 Name Data Format Required? Length Details MethodName String Y18  “RequestLabelStatusResponse” LabelId Alphanumeric Y 8-10 The UniqueID of the Label LabelStatus String Y 7 Label's status ResponseCodeNumeric Y 4 See list of Response Status Codes ResponseMessage String YSUCCESS or FAILURE systemLogId Numeric Y Unique identifier associate tothis specific API call ValidationMessages List<ValidationMessage> NDependent on If the Response Code is 200 the (success), then this willbe omitted. validationMessages If the RequestStatus is not 200 (i.e.,returned the request failed), then this will be populated Contains alist of validation messages, each of which contains the response code,response type (warning or error), and detail message.

The central hub 210 may include an update label service which allowslabel providers to update the ship date of a label by providing thelabel ID of the label they want to update. The label ID is the uniqueidentifier of a label within the system, and can be used in later labelstatus and print requests. Upon receipt, the central hub 210 may updatea record stored in the memory 214 associated with the label ID. Table 15includes examples of information that may be included in an updaterequest.

TABLE 15 Fields Data Format Length Required Details Corresponding SSFLabelId Alphanumeric 8-10 Y The unique ID labelId of the label - mustcorrespond to a valid ID in the system. shipDate Numeric 8 Y Format:SSF: Date of Mailing YYYYMMDD Ship Date must be current or future date.Future date must not exceed max allowable ship date. fileExtensionAlphanumeric 3 or 4 Y Label image file extension (e.g., PDF, JPG, GIF,PNG, etc.) labelImageBase64 Alphanumeric Y Image file as base64 encodedstring

Table 16 includes examples of information that may be included in aresponse message from the central hub 210 for an update request such asfrom a label provider system 220.

TABLE 16 Name Data Format Required Length Details methodName String Y 19e.g. “UpdateLabelResponse” labelDataId String Y 10 The Unique ID of theLabel labelStatus String Y  9 See list of acceptable Label Status CodesresponseCode Numeric Y  4 See list of Response Codes responseMessageString N 27 If the value in the responseCode field <> 200 (i.e., therequest failed), then this field will be replaced with thevalidationErrors field systemLogId Numeric Y Unique identifier associateto this specific API call validationMessages List<Validation N DependentContains a list of validation Messages> on returned messages, each ofwhich validation contains the response code, messages response type(error), and detail message. Any Error messages will result in rejectionof the Request, and a Failure response will be returned. The requestwill not be processed.

In Tables 11-16, reference may be made to label status codes. The labelstatus code indicates the disposition status of a given label associatedwith an item. Table 17 provides examples of label status codes which maybe included in the system.

TABLE 17 Label Status Code Description AVAILABLE Label is active andready for print PRINTED Label has been printed successfullyPRINT_REQUESTED Label has been requested for printing PRINT_FAILED Labelwas unable to be printed VOIDED Label has been voided EXPIRED Label hasexpired (correction to Ship Date can return the Label ID to Availablestatus) PERMANENTLY_EXPIRED Label has permanently expired (the Label canno longer be updated)

In Tables 10-16, reference may be made to response status codes. Aresponse status code may correspond to a predefined identifier that isassociated with a particular response to a request. A code may beassociated with a message type (e.g., error, warning, info), a statusmessage (e.g., success, failure, invalid label ID, missing input value,invalid input value, etc.) and a textual description of the status. Whenproviding status, the code may be used to minimize the data transferredbetween the central hub 210 and label provider 220. A look up table orother data structure may store a mapping between the response statuscodes and the messages and description. The look up table may beimplemented as a service which can be queried using the request statuscode to obtain information about the request status code such as messagetype, status message, or textual description.

The above description discloses several methods and materials of thepresent invention. This invention is susceptible to modifications in themethods and materials, as well as alterations in the fabrication methodsand equipment. Such modifications will become apparent to those skilledin the art from a consideration of this disclosure or practice of theinvention disclosed herein. Consequently, it is not intended that thisinvention be limited to the specific embodiments disclosed herein, butthat it cover all modifications and alternatives coming within the truescope and spirit of the invention as embodied in the attached claims.

The technology is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, handheldor laptop devices, multiprocessor systems, microprocessor-based systems,programmable consumer electronics, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

The present disclosure refers to processor-implemented steps forprocessing information in the system. Instructions can be implemented insoftware, firmware or hardware and include any type of programmed stepundertaken by components of the system.

The one or more processors may be implemented with any combination ofgeneral-purpose microprocessors, microcontrollers, digital signalprocessors (DSPs), field programmable gate arrays (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gated logic, discretehardware components, dedicated hardware finite state machines, or anyother suitable entities that may perform calculations or othermanipulations of information. The system hub 210 may comprise aprocessor 212 such as, for example, a microprocessor, such as a Pentium®processor, a Pentium® Pro processor, a 8051 processor, a MIPS®processor, a Power PC® processor, an Alpha® processor, amicrocontroller, an Intel CORE i7®, i5®, or i3® processor, an AMDPhenom®, A-series®, or FX® processor, or the like. The processors 212and 305 typically have conventional address lines, conventional datalines, and one or more conventional control lines.

The system may be used in connection with various operating systems suchas Linux®, UNIX®, MacOS®, or Microsoft Windows®.

The system control may be written in any conventional programminglanguage such as C, C++, BASIC, Pascal, or Java, and ran under aconventional operating system. C, C++, BASIC, Pascal, Java, and FORTRANare industry standard programming languages for which many commercialcompilers can be used to create executable code. The system control mayalso be written using interpreted languages such as Perl, Python orRuby.

Those of skill will further recognize that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, software stored on a computer-readable medium andexecutable by a processor, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such embodimentdecisions should not be interpreted as causing a departure from thescope of the present invention.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. The steps of a method or algorithm disclosedherein may be implemented in a processor-executable software modulewhich may reside on a computer-readable medium. Memory Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that can be enabled to transfer a computer programfrom one place to another. A storage media may be any available mediathat may be accessed by a computer. By way of example, and notlimitation, such computer-readable media may include RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that may be used to storedesired program code in the form of instructions or data structures andthat may be accessed by a computer. Also, any connection can be properlytermed a computer-readable medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk, and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media. Additionally, the operations of a method oralgorithm may reside as one or any combination or set of codes andinstructions on a machine readable medium and computer-readable medium,which may be incorporated into a computer program product.

The foregoing description details certain embodiments of the systems,devices, and methods disclosed herein. It will be appreciated, however,that no matter how detailed the foregoing appears in text, the systems,devices, and methods can be practiced in many ways. As is also statedabove, it should be noted that the use of particular terminology whendescribing certain features or aspects of the invention should not betaken to imply that the terminology is being re-defined herein to berestricted to including any specific characteristics of the features oraspects of the technology with which that terminology is associated.

It will be appreciated by those skilled in the art that variousmodifications and changes may be made without departing from the scopeof the described technology. Such modifications and changes are intendedto fall within the scope of the embodiments. It will also be appreciatedby those of skill in the art that parts included in one embodiment areinterchangeable with other embodiments; one or more parts from adepicted embodiment can be included with other depicted embodiments inany combination. For example, any of the various components describedherein and/or depicted in the Figures may be combined, interchanged orexcluded from other embodiments.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

As used herein, the terms “determine” or “determining” encompass a widevariety of actions. For example, “determining” may include calculating,computing, processing, deriving, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishing,and the like.

As used herein, the term “selectively” or “selective” may encompass awide variety of actions. For example, a “selective” process may includedetermining one option from multiple options. A “selective” process mayinclude one or more of: dynamically determined inputs, preconfiguredinputs, or user-initiated inputs for making the determination. In someimplementations, an n-input switch may be included to provide selectivefunctionality where n is the number of inputs used to make theselection.

As used herein, the terms “provide” or “providing” encompass a widevariety of actions. For example, “providing” may include storing a valuein a location for subsequent retrieval, transmitting a value directly tothe recipient, transmitting or storing a reference to a value, and thelike. “Providing” may also include encoding, decoding, encrypting,decrypting, validating, verifying, and the like.

As used herein, the term “message” encompasses a wide variety of formatsfor communicating (e.g., transmitting or receiving) information. Amessage may include a machine readable aggregation of information suchas an XML document, fixed field message, comma separated message, or thelike. A message may, in some implementations, include a signal utilizedto transmit one or more representations of the information. Whilerecited in the singular, it will be understood that a message may becomposed, transmitted, stored, received, etc. in multiple parts.

As used herein a “user interface” (also referred to as an interactiveuser interface, a graphical user interface or a UI) may refer to anetwork based interface including data fields and/or other controls forreceiving input signals or providing electronic information and/or forproviding information to the user in response to any received inputsignals. A UI may be implemented in whole or in part using technologiessuch as hyper-text mark-up language (HTML), Flash, Java, .net, webservices, and rich site summary (RSS). In some implementations, a UI maybe included in a stand-alone client (for example, thick client, fatclient) configured to communicate (e.g., send or receive data) inaccordance with one or more of the aspects described.

All references cited herein are incorporated herein by reference intheir entirety. To the extent publications and patents or patentapplications incorporated by reference contradict the disclosurecontained in the specification, the specification is intended tosupersede and/or take precedence over any such contradictory material.

The term “comprising” as used herein is synonymous with “including,”“containing,” or “characterized by,” and is inclusive or open-ended anddoes not exclude additional, unrecited elements or method steps.

What is claimed is:
 1. A system for labeled induction of an item into adistribution network, the system comprising: a label provider configuredto: receive, from a sender communication device, a request for a labelto distribute an item via a distribution network, the request for thelabel including a sender address identifying a location from which theitem is being distributed; create a label based on the request for thelabel; and transmit, to a distribution server, the created label for theitem; and the distribution server in communication with the labelprovider, wherein the distribution server is configured to: receive,from the label provider, the created label; generate a machine-readableidentifier for the label; store, in a data storage device, the createdlabel and an association between the created label and themachine-readable identifier; receive, from an induction communicationdevice, the machine-readable identifier for the label and locationinformation for the induction communication device; retrieve the createdlabel from the data storage device based at least in part on themachine-readable identifier; determine that the location information forthe induction communication device is within a threshold distance of thesender address; and cause, via the induction communication device,generation of a physical label based at least in part on the createdlabel retrieved from the data storage device, wherein the generation ofthe physical label is deferred for a period of time subsequent to thegeneration of the machine-readable identifier and wherein the physicallabel is generated in response to determining that the locationinformation is within the threshold distance of the sender address. 2.The system of claim 1, wherein the distribution server is furtherconfigured to: receive, via the induction communication device, aconfirmation that the physical label has been created; and store, in thedata storage device, an indicator in association with themachine-readable identifier, wherein the indicator indicates that thephysical label has been created.
 3. The system of claim 2, wherein thedistribution server is further configured to: receive, from anothercommunication device, the machine-readable identifier for the label;determine, based on the indicator and the machine-readable identifier,that the physical label has been created; and transmit a message to theanother communication device indicating that the physical label has beencreated.
 4. The system of claim 1, wherein the distribution server isfurther configured to: receive, from a scanning device, scannedinformation from the physical label; confirm that the scannedinformation corresponds to the item; and route the item to an itemprocessing equipment for a distribution network based at least in parton the scanned information.
 5. The system of claim 4, wherein thephysical label includes an identifier indicating that the physical labelwas generated by the distribution server based on a request from thelabel provider, and wherein the item processing equipment includes apostage canceler, and wherein the distribution server is configured toroute the item to bypass the postage canceler in response to receivingthe confirmation.
 6. The system of claim 1, further comprising aninduction receptacle for storing an item, wherein the inductionreceptacle includes: a locking means for securing the inductionreceptacle; and a scanning device for detecting information from thephysical label; and wherein the distribution server is furtherconfigured to: receive, from the scanning device, scanned informationfrom the physical label; retrieve a disposition status for the item fromthe data storage device based at least in part on the scannedinformation, wherein the disposition status indicates whether the itemhas been inducted into the distribution network; determine that the itemhas not been inducted to the distribution network based at least in parton the disposition status; and transmit a message to the locking means,wherein the message causes the locking means to permit access to theinduction receptacle.
 7. The system of claim 1, further comprising alabeling kiosk including an input interface for receiving machinereadable identifiers for labels, wherein receiving the machine-readableidentifier comprises receiving the machine-readable identifier from thelabeling kiosk, and wherein the induction communication device comprisesthe labeling kiosk, and wherein the input interface comprises at leastone of: (a) a scanning device; or (b) a graphical user interface.
 8. Thesystem of claim 1, wherein the created label comprises a data filecontaining information for generating the physical label.
 9. The systemof claim 1, wherein the created label comprises an image of the label.10. The system of claim 1, wherein receiving the machine-readableidentifier comprises receiving the machine readable identifier fromportable, handheld scanning device associated with a distributionresource of the distribution network.
 11. The system of claim 1, whereinthe distribution server is further configured to transmit, to the sendercommunication device, the machine-readable identifier for the label. 12.The system of claim 1, wherein the distribution server is furtherconfigured to transmit, to the label provider, the machine-readableidentifier for the label.
 13. A system for labeled induction of an iteminto a distribution network, the system comprising: one or moreprocessing devices; and a computer-readable storage medium storingmachine readable instructions that, when executed by the one or moreprocessing devices, cause the system to at least: receive, from a labelprovider, information for creating a label for distributing an item viaa distribution network; receive a sender address identifying a locationfrom which the item is being distributed, receive, from the secondcommunication device, location information for the second communicationdevice; create a label using the information for creating the label;generate a machine-readable identifier for the label; store, in a datastorage device, the created label and an association between the createdlabel and the machine-readable identifier; transmit, to a firstcommunication device, the machine-readable identifier for the label;receive, from a second communication device, the machine-readableidentifier for the label; retrieve the created label from the datastorage device based at least in part on the machine-readableidentifier; determine that the location information for the secondcommunication device is within a threshold distance of the senderaddress; and in response to determining that the location information iswithin the threshold distance of the sender address, cause, via thesecond communication device, generation of a physical label based atleast in part on the created label.
 14. The system of claim 13, whereinthe machine-readable instructions, when executed by the one or moreprocessing devices, further cause the system to at least: receive, viathe second communication device, a confirmation that the physical labelhas been generated; and store, in the data storage device, an indicatorin association with the machine-readable identifier, wherein theindicator indicates that the physical label has been generated.
 15. Thesystem of claim 13, wherein the machine-readable instructions, whenexecuted by the one or more processing devices, further cause the systemto at least: receive, from another communication device, themachine-readable identifier for the label; retrieve, from the datastorage device, a disposition status for the item associated with thelabel based at least in part on the machine-readable identifier;determine that the disposition status corresponds to an unauthorizedstatus indicating that the label is no longer authorized for inductingthe item to the distribution network; and transmit a message to theanother communication device indicating that the label is unauthorized.16. The system of claim 13, wherein the physical label includes anidentifier indicating that the physical label was generated based on arequest from the label provider, and wherein the distribution networkincludes a postage canceler, and wherein the machine-readableinstructions, when executed by the one or more processing devices,further cause the system to at least route the item to bypass thepostage canceler based at least in part on a disposition status for theitem.
 17. The system of claim 13, further comprising an inductionreceptacle for storing an item, wherein the induction receptacleincludes: a locking means for securing the induction receptacle; and ascanning device for detecting information from the physical label; andwherein the machine-readable instructions, when executed by the one ormore processing devices, further cause the system to at least: receive,from the scanning device, scanned information from the physical label;retrieve a disposition status for the item from the data storage devicebased at least in part on the scanned information, wherein thedisposition status indicates whether the item has been inducted into thedistribution network; determine that the item has not been inducted tothe distribution network based at least in part on the dispositionstatus; and transmit a message to the locking means, wherein the messagecauses the locking means to permit access to the induction receptacle.18. The system of claim 17, wherein the induction receptacle furtherincludes measurement means configured to collect measurement informationa physical characteristic of the item; and wherein the information forcreating the label includes a specified value for the physicalcharacteristic; and wherein the machine-readable instructions, whenexecuted by the one or more processing devices, further cause the systemto at least: store, in the data storage device, the specified value inassociation with the machine-readable identifier; retrieve, from thedata storage device, the specified value for the label based at least inpart on the machine-readable identifier; and determine that themeasurement information corresponds to the specified value for thephysical characteristic, wherein the message is transmitted afterdetermining that the measurement information corresponds to thespecified value.